Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

Odin Research / What is / Malware and backdoors

What Is the Mozi Botnet? How the P2P IoT Botnet Worked

A peer-to-peer router botnet that spread through weak passwords and old flaws until a signed kill switch shut it down. Its labels still fill threat feeds.

By
Odin by Brandefense
Updated
21 Nov 2026
Reading time
7 min read
Type
IoT botnet

In short

The Mozi botnet is a peer-to-peer botnet of infected IoT devices such as home routers, DVRs and cameras. 360 Netlab documented it in 2019. Bots coordinate over a modified DHT protocol, spread through weak Telnet passwords and known device flaws, and run DDoS attacks. In 2023, a signed kill switch disabled most of the botnet.

Key takeaways

What it is
A peer-to-peer IoT botnet, first captured by 360 Netlab in September 2019 and described as a successor to Hajime.
How it works
Bots join a modified DHT network, accept only ECDSA-signed configurations, brute-force Telnet and exploit known router and camera flaws.
Why it matters
It infected large numbers of devices for DDoS. ESET found a signed kill switch in September 2023, sent by the creators or under pressure from Chinese law enforcement.
What Odin Research saw
263 Mozi endpoints on 261 hosts in 2026 data, none confirmed, all on consumer gateways with no link to attacker servers.
What to do first
Disable Telnet, patch or retire old IoT devices, and use only short-lived blocks for Mozi feed entries.

What is the Mozi botnet?

The Mozi botnet is a peer-to-peer botnet of infected IoT devices, mainly home routers, DVRs and cameras, first documented by 360 Netlab in December 2019. Its bots talk over a modified DHT protocol instead of a central server and can run DDoS attacks. A signed kill switch disabled most of it in 2023.

360 Netlab first captured a sample on 3 September 2019 and named the family after sample file names such as Mozi.m and Mozi.a. Netlab described Mozi as a successor to Hajime, an earlier peer-to-peer IoT botnet built on DHT.

Mozi is a classic botnet. Each infected device is a victim, not an attacker's server. That point matters when a threat feed hands you thousands of "Mozi" addresses.

How the Mozi botnet works

Netlab's 2019 analysis describes the core design:

  • Peer-to-peer over DHT. Mozi builds its network on a modified version of the DHT protocol used by BitTorrent. Netlab notes this helps hide its traffic among normal DHT traffic. New bots join through public DHT nodes and nodes listed in their configuration.
  • Signed configuration. Configuration files carry ECDSA-384 signatures. A bot accepts a new configuration only if the signature checks out, so outsiders cannot simply take over the network.
  • Borrowed code. Many antivirus engines first labelled Mozi as Gafgyt. Netlab found it reuses part of Gafgyt's code, including attack code and some host behaviors.

The configuration tells bots what to do. Netlab lists DDoS attacks with HTTP, TCP and UDP floods, reporting bot details, downloading and running payloads from a URL, updating the bot and running system commands.

How Mozi spreads

According to Netlab, Mozi spreads in two ways:

  1. Weak Telnet passwords. Bots brute-force Telnet logins. On success, they write a downloader that fetches Mozi from another bot's HTTP server.
  2. Known device flaws. Bots exploit published vulnerabilities in routers, DVRs and cameras, including D-Link, Netgear, Huawei HG532, GPON routers and devices built on the Realtek SDK. This is Exploit Public-Facing Application (T1190).

Each new bot joins the peer-to-peer network and starts scanning for the next victim. ESET described Mozi as a botnet that exploited hundreds of thousands of devices each year.

The Mozi kill switch in 2023

ESET reported on 1 November 2023 that Mozi activity fell suddenly in August 2023, first in India on 8 August and then in China on 16 August.

On 27 September 2023, ESET found the cause: a control payload sent inside a UDP message without the usual BitTorrent DHT wrapping. It was sent eight times and told bots to download and install an update over HTTP. That update was a kill switch. ESET says it:

  • stopped the parent Mozi process;
  • disabled services such as sshd and dropbear;
  • replaced the Mozi file with itself and ran device configuration commands;
  • blocked access to several ports with iptables;
  • kept the same foothold and persistence as the original malware.

The payload was signed with the correct private keys. ESET offered two hypotheses: the botnet's creators sent it, or Chinese law enforcement compelled the creators to cooperate. ESET noted that targeting India first and then China suggests a deliberate takedown. For background, see law enforcement takedowns.

What Odin Research observed

Mozi labels still appear in threat feeds in 2026. Odin Research treats the devices behind them as victims.

  • 263 endpoints on 261 hosts, none confirmed. In Monograph 19, Mozi was the second-largest IoT family after Mirai (353). The endpoints sat on consumer gateways and carried router-default certificates.
  • No link to attacker servers. The 618 Mirai, Mozi and Moobot endpoints in that study shared no address with the C2 or cracking servers, and no traffic between them was observed.
  • Rotating addresses. Nine Mozi endpoints in Monograph 19 sat on subscriber telecom networks, where addresses pass to new households. Monograph 13 lists a suspected Mozi peer on port 443 on a Chinese telecom network as an example of why a permanent block fails.
  • A small share of C2 feeds. In Monograph 02, Mozi made up 42 records in an IoT slice of 203, next to Mirai (112) and Hajime (49).

The lesson: a Mozi-labelled address is almost always someone's infected router. Block it briefly if you must, never permanently.

How to detect Mozi

  • DHT traffic from devices that should not use it. Routers, cameras and DVRs have no reason to join BitTorrent-style DHT networks.
  • Telnet scanning. Outbound Telnet attempts to many addresses from an IoT device point to an infected bot.
  • Unexpected HTTP downloads. A device fetching binaries from another consumer IP is a classic botnet propagation sign.
  • Locked-out management. Because the kill switch disabled sshd and changed firewall rules, a device that suddenly blocks its own admin access may have been infected.
  • Feed hygiene. Expire Mozi feed entries quickly. Old peers on rotating addresses create false positives.

Odin Research does not publish a dedicated Mozi rule. Its Defense Kit holds the rules from the reports above, and Monograph 19 explains how to handle router addresses in feeds.

How to defend against Mozi and similar IoT botnets

  1. Disable Telnet on routers and IoT devices, and change default passwords.
  2. Patch or replace old devices. Mozi relied on published flaws in end-of-life routers and cameras.
  3. Keep IoT off the internet. Do not expose device management to the internet, and put IoT on its own network segment.
  4. Reboot and reflash after infection. Then restore the vendor firmware and reset credentials, since the kill switch left changes behind.
  5. Use short-lived blocks for feed entries on consumer networks. Learn how threat feeds work before you automate them.

Mozi botnet compared with other IoT botnets

BotnetDesignOdin countNotes
MoziPeer-to-peer over DHT, signed configs263 endpoints (Monograph 19)Disabled by a signed kill switch in 2023
MiraiIoT botnet family353 endpoints (Monograph 19)63 protocol-confirmed infections in that study
HajimePeer-to-peer over DHT49 records (Monograph 02)Netlab calls Mozi its successor
MoobotIoT botnet family2 endpoints (Monograph 19)Rare in Odin data

For a cloud-focused worm that also uses peer-to-peer links, see P2PInfect.

Frequently asked questions about Mozi botnet

What is the Mozi botnet?

Mozi is a peer-to-peer botnet of infected IoT devices such as routers, DVRs and cameras. Its bots coordinate over a modified DHT protocol and can run DDoS attacks.

Is Mozi still active?

ESET reported that a kill switch disabled most Mozi bots in August and September 2023. Mozi labels still appear in threat feeds, but Odin Research found no confirmed Mozi C2 in its 2026 data.

Who killed the Mozi botnet?

ESET does not know for sure. It suggested either the botnet's creators or Chinese law enforcement compelling them, because the kill switch was signed with the correct private keys.

How did Mozi spread?

360 Netlab says Mozi brute-forced weak Telnet passwords and exploited known flaws in routers, DVRs and cameras from vendors such as D-Link, Netgear and Huawei.

Is Mozi based on Mirai?

360 Netlab found that Mozi reuses part of the Gafgyt code, including attack code. It described Mozi as a successor to the Hajime peer-to-peer botnet.

Should I block Mozi IP addresses?

Only briefly. Mozi addresses are almost always infected home routers on rotating consumer lines, so a permanent block mostly hurts the next customer.

How do I protect my router from Mozi?

Disable Telnet, change default passwords, install firmware updates or replace end-of-life devices, and do not expose device management to the internet.

Mozi vs Mirai: what is the difference?

Both are IoT botnets. Mozi uses a peer-to-peer DHT network with signed configurations instead of central servers. In Monograph 19, Odin Research counted 353 Mirai and 263 Mozi endpoints.

Sources

  1. 360 Netlab, "Mozi, Another Botnet Using DHT", 23 December 2019. blog.netlab.360.com/p2p-botnet-mozi/ (checked 21 November 2026)
  2. ESET WeLiveSecurity, "Who killed Mozi? Finally putting the IoT zombie botnet in its grave", 1 November 2023. www.welivesecurity.com/en/eset-research/who-killed-mozi-finally-putting-the-iot-zombie-botnet-in-its-grave/ (checked 21 November 2026)

Related tools and terms

All Odin Research explanations · Brandefense glossary

Odin Research

Get the rules, not just the definition

Every Odin Research report ships with verified indicators and detection rules you can load today.

Open the Defense Kit