Mylobot is a long-running Windows malware family and botnet best known for converting infected systems into backconnect proxy nodes while also maintaining downloader functionality for additional payload delivery. Public reporting has tracked the family since 2018, with evidence that its core loader architecture predates that disclosure and remained active for years afterward at substantial scale.
The malware ecosystem includes multiple components, notably a proxy-focused bot and a downloader component often referred to as mylobot-core, both commonly delivered through a shared packer and shellcode-based loader. That loader resolves Windows APIs dynamically, decrypts embedded resources, and launches later stages through process hollowing into a newly created host process. The downloader stage performs anti-virtual-machine checks, contacts encrypted command-and-control infrastructure, reports basic host information, and retrieves subsequent payloads, most commonly another Mylobot component.
Mylobot’s primary operational role is proxy enablement. Infected hosts can be instructed to relay traffic, maintain persistent command-and-control sessions, and service remote connection tasks, effectively turning victim machines into residential-style proxy infrastructure. Telemetry and infrastructure analysis have repeatedly linked the botnet to the BHProxies proxy service, supporting the assessment that monetization through proxy access is a central purpose of the operation. Researchers have also observed commands for downloading and executing additional binaries, mainly for self-update and component refresh, though Mylobot has at times been associated with delivery of other malware.
Network behavior associated with Mylobot includes extensive domain discovery activity, including large volumes of DNS requests to hardcoded or algorithmically varied subdomains, followed by persistent command-and-control connectivity once a live server is found. Some variants used fake-DGA-style domain lists, while later proxy-focused versions reduced or changed that approach. The downloader component has continued to use encrypted hardcoded domain sets and runtime decryption to locate next-stage infrastructure.
Mylobot targets Windows systems and has been observed globally at significant infection volume. Reporting has identified especially high victim concentrations in countries including India, the United States, Indonesia, and Iran during some observation periods. The malware is primarily associated with cybercriminal monetization through proxy services, although isolated observations indicate the operators may also have experimented with adjacent criminal activity such as spam or extortion-related tooling.
Mallory pivots from this family to the IOCs, detections, and named campaigns that touch your stack, and pages you when something new lands.
9 distinct techniques documented for this family, organized by ATT&CK tactic.
All the malicious software used by Mylobot is packed and loaded by Packer-Shellcode... The purpose of packing the malicious software is to evade direct detection.
Mylobot-proxy transforms compromised machines into network proxy nodes, forwarding traffic through C2 (Command and Control) issued proxy tasks.
When Mylobot receives an instruction from the C2, it transforms the infected computer into a proxy. The infected machine will be able to handle many connections and relay traffic sent through the command and control server.
Message ID (msg_id) Description ... 7 Download a binary using HTTP 8 Download multiple binaries using HTTP + delay (8 hours)
For each of these domains, the sample tries to connect to many of its subdomains. Most subdomains will start with the letter x, w, or m, followed by a number.
84 indicators attributed across vendor reports, sandbox runs, and researcher write-ups. Full values are available in Mallory.
IPs, domains, and DNS infrastructure linked to this family.
File hashes (MD5, SHA-1, SHA-256) from samples and reports.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Mentioned only in appendix literature as a proxy botnet example.
Windows-focused botnet family operated by the Mylobot group. It uses packed multi-stage malware, fake-DGA domains in some components, process hollowing, and C2-controlled payload delivery. Its operations center on monetizing infected hosts as proxy nodes via mylobot-proxy, while mylobot-core acts mainly as a downloader for subsequent payloads.
Mylobot is described as a proxy bot that generates large volumes of DNS requests, connects to hardcoded C2 domains, keeps persistent connections open, and turns infected machines into proxies that relay traffic. It also has downloader functionality or is distributed by a downloader variant that retrieves additional stages, including updated Mylobot payloads.
Match every observed IP, domain, and hash against your live telemetry.
Named campaigns wielding this family, with evidence pinned to each claim.
CVEs this family uses for access and lateral movement.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Every documented technique, ranked by evidence weight.
Reddit, Mastodon, and CTI community discussion around this family.