Glossary

Botnets: compromised devices working together

Learn how a malicious botnet coordinates compromised devices, why routers and connected appliances matter, and what an alert or a clean computer scan can establish.

Definition

In a security context, a botnet is a network of compromised devices that an attacker can coordinate remotely to perform activities without their owners’ authorization.

Also called: bot network, zombie network, malicious botnet, botnet malware

A bot is one member; the botnet is the collection

A malicious botnet combines access to multiple compromised devices. Each member can act as a bot, while the attacker coordinates activity across the collection. The device owner may see ordinary operation while its resources are used for another purpose.

The term is most useful when describing that coordinated control. It does not identify one malware family, one operating system, or one method of infection. Malwarebytes’ botnet overview discusses compromised members and the control arrangements used to direct them, including centralized and peer-to-peer structures.

Not every automated program is malicious. Search crawlers, approved monitoring agents, and other software can perform repeated tasks legitimately. This article uses “botnet” in the security sense of devices controlled without authorization, rather than treating automation itself as evidence of infection.

An illustrative example is a group of compromised devices instructed to send traffic to the same service. Each contributes a fraction of the traffic; their combined activity creates the wider effect. That example explains coordination, not a test that can identify a botnet from one device’s bandwidth use.

What attackers can use the collection for

A botnet can provide resources for different operations. The particular malware and controller determine the functions available; not every member performs every task.

UseWhat the compromised devices contributeWhat should not be inferred automatically
Distributed denial of serviceTraffic intended to overwhelm another serviceThat every network slowdown is such an attack
Spam distributionCapacity to send unwanted messagesThat the owner’s email account necessarily sent them
Malware deliveryA route to distribute additional malicious componentsThat every possible payload arrived
Criminal proxy serviceA way to relay someone else’s traffic through compromised infrastructureThat an observed address identifies the person responsible

Malwarebytes describes denial-of-service, spam, and malware distribution as botnet uses. A distinct example comes from the FBI’s May 2025 router advisory, which describes TheMoon malware and criminal proxy services on compromised routers.

This last use explains why unauthorized activity can involve a household’s internet connection even when its main laptop has no related detection. The network address is an observation about where traffic appears to come from, not by itself proof of who initiated it.

Botnet, worm, and backdoor describe different roles

A worm describes replication. A backdoor describes an access mechanism. A botnet describes coordinated compromised members. Malware that spreads between devices can recruit members, and a backdoor can provide control, but neither feature makes the terms synonyms.

Similarly, a Trojan or downloader can participate in delivery. The botnet label alone does not establish which route brought the code onto your device or whether it can spread onward automatically.

Microsoft’s classification criteria separately describe command-and-control behavior: malware communicates with attacker infrastructure to receive instructions. That communication role helps explain coordination, but a category name still does not establish the specific commands executed in an individual incident.

Routers and connected appliances belong in the scope

A security investigation should not assume that “device” means only a desktop computer. Routers, streaming devices, and other internet-connected equipment can be involved, depending on the campaign.

The FBI’s June 2025 BADBOX 2.0 advisory describes compromised connected products, with infection occurring before purchase or through malicious applications. It also cautions that an indicator alone does not establish malicious activity. These are findings about that campaign, not a claim that every unfamiliar brand or Android device is infected.

An ordinary laptop scan examines the laptop within the scanner’s scope. It does not inspect every router, television accessory, or other appliance sharing the connection. A clean result should not be expanded into a certificate for the entire household network.

For network equipment, use the manufacturer or service provider’s supported investigation and recovery process. Installing a Windows cleaner on a nearby computer does not remediate a separate appliance.

An alert needs the affected device and evidence

Unusual traffic, frequent connection problems, and high resource use can have ordinary causes. They need corroboration before assigning a botnet diagnosis. A blocked connection also does not by itself prove that the sender successfully received instructions or performed an attack.

Record who issued the warning, its time, and the device or connection it concerns. If an internet provider sends a notification, verify it through an independently obtained official contact route. Avoid installing a tool from an unexpected warning or giving remote access to someone who calls about it.

Where a local security product identifies an item, keep its path, detection name, and action. Use the infection diagnostic for unexplained symptoms, while recognizing that it does not cover every kind of connected appliance.

Recovery addresses members and the route back in

For a credibly affected personal device, limit its network use while obtaining appropriate support. On a managed network, report the evidence to IT and follow its incident process. Removing one member does not establish that other devices are unaffected.

The FBI’s router advisory recommends current firmware and replacing unsupported equipment where possible. Confirm support status and recovery instructions with the actual manufacturer; avoid improvised firmware downloads or resets based only on the word “botnet.” Preserve relevant settings and evidence before changes when incident support requires them.

Recovery should identify the affected device, the unauthorized software or configuration, completed remediation, and the route that permitted compromise. If activity returns, compare the evidence and device identity rather than repeatedly scanning the same laptop. A wider network finding needs a response with a matching scope.

Sources & documentation

Sources checked on 6 Oct 2026. Documentation research does not establish independent testing.

MalwareCleanupTools

Guides based on official documentation. About our content · Corrections policy