| Architecture | Pros | Cons | Examples | Detection |
|---|---|---|---|---|
| Centralized (IRC/HTTP) | Simple to implement, easy command distribution, fast updates | Single point of failure, easy to take down, traceable | Zeus, Necurs, early botnets | Easy |
| P2P (Decentralized) | No single point of failure, resilient, hard to take down | Complex to implement, slower updates, more traffic | Conficker, ZeroAccess | Difficult |
| Hybrid | Balanced approach, fallback mechanisms, flexible | Increased complexity, multiple detection vectors | Mirai variants, modern botnets | Moderate |
Target machine is compromised through exploit, phishing, drive-by download, or other attack vector. Malware payload is installed.
Bot establishes initial connection to C2 infrastructure. Registers with botnet, sends system information, awaits further instructions.
Bot receives commands from C2 server. Commands may include: update malware, execute DDoS, steal data, install additional payloads.
Bot executes received commands. May perform DDoS attacks, send spam, mine cryptocurrency, steal credentials, or propagate to new targets.
Bot maintains persistence on infected system. Receives updates, new commands, and evolves to evade detection. Cycle repeats.