Skip to content
Cybersecurity

Botnet

A botnet is a network of infected computer devices (called bots or zombies) that are remotely controlled by cybercriminals. The name botnet comes from combining the words 'robot' and 'network'. Botnets consist of many devices - from personal computers to IoT devices - that have been infected with malware allowing the attacker (botmaster) to take control of them without the owners' knowledge.

Botnet Definition

Botnet is a network of infected computer devices (called bots or zombies) that are remotely controlled by cybercriminals. The name botnet comes from combining the words “robot” and “network”. Botnets consist of many devices - from personal computers to IoT devices - that have been infected with malware allowing the attacker (botmaster) to take control of them without the owners’ knowledge.

How Does a Botnet Work?

Botnet operation can be divided into several stages:

  • Infection: The attacker spreads malware that infects devices.

  • Taking Control: Infected devices connect to the command and control (C&C) server.

  • Waiting for Orders: Bots remain dormant, waiting for commands from the botmaster.

  • Attack Execution: On the botmaster’s command, all bots simultaneously perform specified actions.

Types of Botnets

  • Centralized: Based on a client-server model, where all bots communicate with a central C&C server.

  • Decentralized (P2P): Bots communicate with each other, making botnet detection and neutralization more difficult.

  • Hybrid: Combine features of both above models.

Typical Botnet Uses

  • DDoS (Distributed Denial of Service) attacks
  • Spam distribution
  • Theft of personal and financial data
  • Cryptojacking (illegal cryptocurrency mining)
  • Malware distribution
  • Conducting brute-force attacks

How Do Devices Become Part of a Botnet?

  • Through exploits using security vulnerabilities
  • Phishing and social engineering
  • Infected email attachments
  • Malicious websites
  • Unsecured IoT devices

Botnets in the Workplace — Which Devices Get Hijacked and How Do You Spot It?

A botnet does not have to be built by whoever uses it. The MITRE ATT&CK knowledge base (technique T1583.005) describes attackers buying, leasing or renting ready-made networks of compromised systems — including as a subscription to “booter/stresser” services — and then using them for large-scale phishing, DDoS attacks or as a relay network that hides their own infrastructure. The same description notes that internet-facing edge devices no longer supported by their manufacturer are commonly pulled into botnets, along with small-office routers, VPS servers and IoT devices.

For a business this means two risks. First, an old router, camera or video recorder on its network may be working for someone else’s botnet and attacking others from the company’s IP address. Second, the company may itself become the target of a denial-of-service attack — MITRE (technique T1498) describes it as exhausting the bandwidth that the website, email, DNS or web applications depend on, and lists extortion among the goals of such attacks.

Two families well documented by the US agency CISA show both infection routes:

  • Mirai — malware that mainly took over home routers, network cameras and video recorders still using their default passwords; publication of its source code raised the risk of further botnets. CISA recommends, among other things, replacing default passwords with strong ones, applying updates, disabling UPnP on routers unless it is needed, and watching for Telnet login attempts on ports 23 and 2323.
  • Emotet — a trojan acting as a gateway for other malware, sent in phishing email attachments and links and spreading through the network like a worm; CISA noted that Emotet botnets dropped TrickBot (leading to ransomware) and Qakbot onto victims’ systems.

The warning sign is therefore traffic a device should not be generating: outbound connections to unknown addresses, login attempts from outside on administrative services, a sudden load on the internet link. Detecting this kind of activity and responding quickly — for example by isolating the infected host — is what our Managed Detection and Response (MDR) service provides.

Threats Associated with Botnets

  • Privacy and personal data loss
  • Decreased performance of infected devices
  • Resource utilization for illegal activities
  • Exposure to additional attacks and infections
  • Financial losses for companies and organizations

Botnet Detection Methods

  • Network traffic analysis
  • System behavior monitoring
  • Log analysis
  • Using intrusion detection and prevention systems (IDS/IPS)
  • Advanced behavioral analysis

Protection Against Botnets

  • Regular system and software updates
  • Using strong passwords and two-factor authentication
  • Using antivirus software and firewalls
  • User education in cybersecurity
  • Network segmentation and privilege limitation

Famous Botnet Attack Examples

  • Mirai: IoT botnet responsible for massive DDoS attacks in 2016.
  • Zeus: Specializing in banking data theft.
  • Conficker: One of the largest botnets, infecting millions of computers.
  • Gameover Zeus: Advanced botnet used for financial attacks.
  • Emotet: Modular botnet used for malware distribution.
  • DDoS - primary use of botnets
  • Malware - malicious software creating botnets
  • Trojan - malware type often used for botnet building
  • Cryptojacking - cryptocurrency mining by botnets

Explore Our Services

Want to protect your organization against botnets? Check out:

Botnets pose a serious threat to cybersecurity, requiring constant vigilance and comprehensive protection measures from both individual users and organizations.

Frequently asked questions

+ What exactly is a botnet and how does it work?

A botnet is a network of infected devices (bots, zombies) remotely controlled by an attacker (botmaster) via Command & Control (C2/C&C) infrastructure. Lifecycle: (1) Initial infection — exploit, phishing, supply chain compromise, RDP/SSH brute force, unsecured IoT (default passwords). (2) Persistence — boot autostart, registry keys, scheduled tasks, fileless in memory. (3) C2 communication — bot connects to C&C server (HTTP/HTTPS, IRC, DNS tunneling, Tor, Telegram, P2P) and waits for commands; modern botnets use DGA (Domain Generation Algorithms) — randomly generated C&C domains the attacker registers seasonally. (4) Command execution — DDoS, spam, data theft (banking, credentials), cryptojacking, ransomware delivery, anonymization proxy, click fraud. Scale varies widely: according to the FBI, industry experts estimated that Mariposa may have infected as many as 8–12 million computers, while Mantis (2022), according to Cloudflare, ran on about 5,000 hijacked virtual machines and servers and still generated an attack of 26 million HTTPS requests per second. A botnet can also be a service: according to MITRE ATT&CK (T1583.005), criminals buy, lease or rent access to a ready-made network of compromised devices, including as a subscription to booter/stresser services.

+ What is the difference between a botnet and a DDoS attack?

A botnet is a tool — a network of compromised devices that an attacker can give a shared command. DDoS is one of the attacks it can be used for: flooding a target with traffic from many systems at once to exhaust the bandwidth and take down a website, email or DNS. The MITRE ATT&CK knowledge base lists botnets as one way of generating such traffic, alongside spoofing other IP addresses. The same botnet can, however, also be used to send phishing or as a relay network.

+ What should you do with an IoT device infected by a botnet?

For devices infected with Mirai, the US agency CISA recommends: disconnect the device from the network and the internet, reboot it (this malware lives in memory, so a reboot removes it), change the default password to a strong one and only then reconnect the device — otherwise it will quickly be reinfected. Firmware updates should follow as soon as they are available. The reboot advice applies to Mirai — with other families a reboot alone may not be enough, so in a business setting an infected device is worth handing over to the security team for analysis.

+ What types of botnets exist by C&C architecture?

Three main models: (1) Centralized (client-server) — all bots communicate with one or a few C&C servers; protocols: HTTP/HTTPS (Zeus, Citadel), IRC (classic, GTbot), Tor hidden services (newer botnets), Telegram (latest C&C-as-a-service). Easy to orchestrate but single point of failure — C&C takedown kills the botnet. (2) Decentralized (P2P) — bots communicate using protocols like Kademlia DHT; examples: Storm, Waledac, Sality, Gameover Zeus, Mozi (IoT). Resilient against takedown but slower command propagation (P2P latency). (3) Hybrid — combines both: super-peers act as mini-C&Cs, normal bots connect to them P2P. Conficker C/D, ZeroAccess. Newer trends: (a) DGA + DoH — algorithmic domains resolved via DNS-over-HTTPS to evade DPI, (b) Domain fronting — C&C hidden behind legitimate CDNs (CloudFront, Fastly), (c) Telegram/Discord C&C — easy setup, hard takedown because legitimate platforms, (d) Living-off-the-cloud — C&C in GitHub Gists, Pastebin, Google Docs.

+ What are the most famous botnets in history?

A few botnets that made history (the order is not a ranking): Mariposa — according to the FBI, industry experts estimated it may have infected as many as 8–12 million computers; it stole passwords as well as card and bank account data, launched denial-of-service attacks and spread viruses, and in 2010 the FBI announced the arrest of its creator and operators. Necurs — observed since 2012, according to Microsoft it infected more than 9 million computers and distributed, among others, the GameOver Zeus banking trojan. Mirai (2016) — took over home routers, network cameras and video recorders with default passwords; the publication of its source code raised the risk of further IoT botnets. Emotet — a trojan that usually acts as a downloader of other malware and delivered TrickBot and Qakbot, among others, to its victims; its infrastructure was taken over in January 2021. Mantis (2022) — according to Cloudflare, about 5,000 hijacked virtual machines and servers rather than IoT devices, yet it generated an attack of 26 million HTTPS requests per second. Other well-known names include Storm, Conficker, Zeus, Cutwail, Mozi and Anubis/Cerberus.

+ How do IoT botnets differ from traditional ones?

IoT botnets have unique dynamics: (1) Potential scale — there are a great many IoT devices, and every camera/router/lamp is a potential bot. (2) Weak security — default passwords (admin/admin, root/12345), no update process, embedded Linux with old, unpatched vulnerabilities, no antivirus. (3) Always-on, broadband — IoT devices run non-stop and often have a fast connection, which makes them a good DDoS tool. (4) Unified exploits — port scanning 23/2323 (Telnet), 22 (SSH), 7547 (TR-069), 81/8080 (HTTP admin); one exploit can infect a very large number of identical devices. (5) Hard remediation — user doesn't know router is infected; only fix is factory reset + firmware update (many users won't do it). Top IoT botnets: Mirai (cameras, DVRs), Mozi (Netgear, D-Link, Huawei routers), Hajime, Reaper/IoTroop, Persirai, BrickerBot (sabotage — destroyed devices to 'clean' them from Mirai), Echobot, Hide and Seek (P2P, persistence through reboot — rare in IoT). Defense: change default passwords, VLAN segmentation for IoT, monitor outbound traffic (a camera shouldn't connect to unknown IP addresses on the internet), firmware updates, block Telnet/SSH at network edge, use devices from vendors with patch programs.

+ How to detect and analyze botnet traffic?

Five layers of detection: (1) Network-level — DNS traffic analysis (anomalous query frequency, queries to newly registered domains, ML-based DGA detection), beaconing detection (C&C check-ins at regular intervals with random variation — jitter), Tor/I2P traffic, unexpected ports (IRC 6667, custom). (2) Endpoint — EDR/AV malware-as-bot detection, persistence mechanisms (autorun, scheduled tasks, services), unusual process trees (cmd.exe spawned by browser), connections to known C&C IPs. (3) Behavioral analytics — UEBA detects accounts sending an unusually high volume of email (spam bot), a miner keeping the CPU fully loaded without user activity, a device participating in internal network scanning (lateral movement). (4) Threat intelligence feeds — Spamhaus DROP/EDROP, abuse.ch (Feodo Tracker, ThreatFox), CIRCL, MISP communities, commercial (Recorded Future, Mandiant Advantage); block communication to known C&C IPs/domains. (5) Sinkhole analysis — researchers seize C&C domains (after DGA registration expiration) and log connecting IPs — enables mapping of infected devices. Tools: Zeek (Bro) with botnet-detection scripts, Suricata with ET Open ruleset, Wireshark for deep analysis, Joe Sandbox / Cuckoo for dynamic malware sample analysis, Maltego for C&C infrastructure mapping.

+ What were the largest botnet takedowns and what did they teach us?

A few operations that showed how botnets are taken down (in chronological order, not a ranking): Mariposa (2010) — the FBI, together with the Slovenian Criminal Police and the Spanish Guardia Civil, announced the arrest of the botnet's creator and operators. Avalanche — a network dismantled on 30 November 2016, after more than four years of investigation by the Public Prosecutor's Office in Verden and the Lüneburg Police (Germany), carried out in cooperation with, among others, the US Department of Justice, the FBI, Europol and Eurojust. Necurs (2020) — Microsoft and partners across 35 countries; under a US federal court order Microsoft took control of Necurs infrastructure in the United States, and analysis of its domain generation algorithm made it possible to predict over 6 million domains that would be created in the next 25 months and report them to registries for blocking. Emotet (January 2021) — according to Europol, a joint action by authorities in the Netherlands, Germany, the United States, the United Kingdom, France, Lithuania, Canada and Ukraine ended with investigators taking control of the botnet's infrastructure. Lessons: (a) an effective action requires international coordination, because operators and servers are spread across many jurisdictions; (b) a botnet that generates domains algorithmically (DGA) can be weakened by predicting and blocking its domains in advance; (c) taking over infrastructure without arresting the operators does not guarantee the botnet will not return; (d) after the infrastructure is taken over, the owners of infected devices need to be reached (sinkholing and victim notification).

+ How to protect an organization from being included in a botnet?

Layered defense: Prevention (stop infection): (1) Patch management — botnets commonly exploit known CVEs; apply patches within the deadlines set by your vulnerability management policy, critical ones first, plus automatic OS and browser updates. (2) EDR/XDR — endpoint protection detecting persistence mechanisms and C2 traffic. (3) Email security — anti-phishing (Proofpoint, Mimecast), attachment sandboxing (FireEye, Cloudflare Area 1). (4) Web filtering — SWG blocks known C&C domains, 'malware', 'newly registered domains' categories. (5) MFA everywhere — protects against credential-stuffing botnets. (6) IoT hardening — change default passwords, VLAN segmentation, block Telnet/SSH/UPnP at edge. Detection: (7) DNS firewall (Cloudflare Gateway, Cisco Umbrella) — blocks C&C queries; log all DNS queries. (8) NetFlow analysis — anomalous outbound connections, beaconing patterns. (9) TI feeds integrated with firewall/SIEM — automatic blocking of known C&C IPs. Response: (10) IR playbook for 'host communicating with C&C' — network isolation, EDR triage, image collection, reimage. (11) Threat hunting — proactive hunt for indicators (Sysmon logs, autoruns, scheduled tasks). (12) Post-incident — root cause analysis (how was it infected?), strengthen the layer that failed. Useful frameworks: MITRE ATT&CK (TA0011 Command and Control), CIS Controls v8 (controls 4, 9, 10, 13), NIST CSF (Detect, Respond functions).

Tags:

botnet malware DDoS zombie cybercrime

Want to Reduce IT Risk and Costs?

Book a consultation - we respond within 24h

Response in 24h Custom quote No obligations