Skip to content
NewA calmer, faster ZeroHour
Malwaremedium

TuxBot v3: Inside an IoT Botnet Framework With LLM

Palo Alto Unit 42by Asher Davila, Chris Navarrete, Doel Santos ()13 min read4 · 2 reads
AI summary · glm-5.3-flashSummaries by Vani AI

Unit 42 uncovers TuxBot v3, an LLM-assisted IoT botnet framework with 17-architecture builds, Telnet brute-forcing, and DDoS capabilities.

Palo Alto Unit 42 identified TuxBot v3 Evolution, a modular IoT botnet framework derived from AISURU, Wuhan-lineage botnets, and MHDDoS. The C-based bot brute-forces Telnet with 1,496 credential pairs, targets over 30 IoT device families, and communicates with a Go-based C2 over encrypted TCP with multiple fallback mechanisms including DGA, P2P, and DNS TXT. LLM-assisted development left hallucinated crypto implementations and broken exploit modules in the analyzed samples, though roughly 70% of core functionality works. Researchers warn polished production builds likely exist, raising the threat potential.

Key facts
  • Bot cross-compiles for 17 architectures including ARM, MIPS, x86_64, and RISC-V
  • LLM-generated code shipped with hallucinated crypto and broken exploit modules
  • Fallback C2 includes SHA512 DGA, P2P gossip with Ed25519-signed commands, IRC, and DNS TXT
  • Framework recovered with full source code, binaries, and 254 automated DDoS benchmark reports
  • Telnet brute-forcing with 1,496 credential pairs remains a viable infection vector
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

Indicators of compromise

auto-extracted · verify before use · export allAll
TypeIndicatorContext
domaindigikalas.onlinebdirectory leaks the workstation hostname newtuxdev.sevielw.digikalas[.]online Aug. 6, 2025 Developer domain digikalas[.]online register
ipv4185.10.68.127efore deployment. The source code contains an IP address of 185.10.68[.]127 , which we pivoted on to link TuxBot to Keksec/Kaitori (a
ipv4209.182.237.133d with symbols March 5, 2026 C2 server first seen on Xpanse 209.182.237[.]133:2222 , banner SSH-2.0-CNC-Control-Server April 22, 2026 S
ipv48.8.8.8l Implementation Status DNS TXT Queries c2.tuxbot.local via 8.8.8[.]8 Functional DGA Seed format <YYYY-MM-DD>-TuxBotv3-Evolutio
sha25671dfbb171eca4ef9d02ff630b56e5283bbef7b375d4dbe9e8c9531bef312fa8d6 The first TuxBot sample appears on VirusTotal SHA256 hash 71dfbb171eca4ef9d02ff630b56e5283bbef7b375d4dbe9e8c9531bef312fa8d , x86_64 debug build with symbols March 5, 2026 C2 server f
urlhttp://127.0.0.1/cmdCHANNEL #tuxbot TABLE_IRC_NICK_PREFIX tux TABLE_HTTP_C2_URL hxxp[:]//127.0.0[.]1/cmd TABLE_THINKPHP_PAYLOAD Full HTTP GET request (312 bytes

From the original article

13 min read at unit42.paloaltonetworks.com

We identified a previously undocumented modular internet-of-things (IoT) botnet framework named TuxBot v3 Evolution. The malware authors leveraged an LLM to assist in their code development, yielding mixed results. While the AI complied with their request to generate botnet code, it included a safety disclaimer that the developer failed to remove before shipping.

Palo Alto Unit 42

By Asher Davila, Chris Navarrete, Doel Santos · unit42.paloaltonetworks.com

Read the full article at Palo Alto Unit 42

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.