Skip to main content
Mallory
← Back to News
botnet-infrastructureembedded-device-vulnerabilitydefault-credential-exposureremote-access-implant

Hajime IoT Worm Built a 300,000-Node Peer-to-Peer Botnet

Malware Intelligence · 2 sources · Updated 5mo ago · First seen May 25, 2026

Hajime IoT Worm Built a 300,000-Node Peer-to-Peer Botnet

The Hajime malware infected nearly 300,000 internet-connected devices by combining multiple compromise methods against routers, cameras, DVRs, and cable modems. Researchers reported that the worm spread through Telnet default-password attacks, added a TR-069 exploitation module for remote code execution, and abused an Arris cable modem password-of-the-day mechanism, allowing it to compromise vulnerable IoT systems at scale. The botnet used a peer-to-peer architecture and tailored downloader binaries to victim device architectures and WAN interfaces, while also refining banner-based brute-forcing and architecture detection to improve infection success.

Victimology data showed broad global exposure, with the highest concentrations of infected hosts observed in Iran, Brazil, Vietnam, Russia, and Turkey. DHT leecher analysis identified 297,499 unique infected hosts, and honeypot telemetry indicated many victims were consumer and small-office embedded devices. Despite the botnet’s size and continued evolution, researchers said they had not observed Hajime being used for overt attacks at the time of reporting, leaving its ultimate purpose unclear even as it was tracked as Backdoor.Linux.Hajime.

Hunt this familyPull IOCs and campaign context straight into your stack.
Get the IOCs
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

4 events · Oct 16, 2016 – Jun 8, 2017
  1. Jun 8, 20179y ago

    Kaspersky says Hajime's purpose remains unclear despite continued growth

    In its June 2017 report, Kaspersky said it had not observed Hajime being used for overt attacks or other malicious activity, even as the botnet continued to expand. The company detected the malware as Backdoor.Linux.Hajime.

  2. Jun 8, 20179y ago

    Researchers observe Hajime botnet nearing 300,000 infected devices

    Kaspersky reported that Hajime had grown into a peer-to-peer botnet with 297,499 unique infected hosts identified through DHT leecher analysis, affecting many DVRs, cameras, and routers worldwide. The largest concentrations of infections were observed in Iran, Brazil, Vietnam, Russia, and Turkey.

  3. Jun 8, 20179y ago

    Hajime expands propagation with new exploitation methods

    By the time of Kaspersky's analysis, Hajime had evolved beyond Telnet default-password attacks to add a TR-069 exploitation module and an Arris cable modem password-of-the-day attack, improving its ability to compromise IoT devices via remote command execution and credential abuse.

  4. Oct 16, 201610y ago

    Hajime IoT worm is first publicly reported

    The Hajime malware family was first publicly reported in October 2016 as an IoT worm spreading through vulnerable internet-connected devices.

Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Malware

1 linked
Do you run this?Pull the IOCs, campaigns, and victimology behind this family, ready to push into your SIEM and EDR.
Hunt This Malware
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.