C2
How it works
After a host is breached, an implant (beacon/agent) is installed that periodically connects back to a C2 server controlled by the attacker. The server pushes commands (e.g. download files, launch another module, spread laterally), and the implant returns results. To evade detection, the traffic is disguised as ordinary communication (HTTP/S, DNS, requests to popular cloud services), encrypted, and often spread out over time (beaconing with randomized jitter). For resilience, multiple layers are used: domain generation algorithms (DGA), fallback channels, proxies, and tunneling, so blocking one address does not sever control. Defenders detect C2 by analyzing traffic patterns, domain/IP reputation, and indicators of compromise (IOCs) fed into SIEM/EDR systems, then block or sinkhole the attacker's infrastructure.
Problem solved
After gaining access to a system, an attacker needs a persistent, undetectable way to issue commands, exfiltrate data, and update malware — without physical access and without triggering alarms. C2 solves this by providing a covert, disruption-resistant channel for managing compromised infrastructure.