Beacon Analysis
Also called beacon detection.
Finding C2 callbacks by their periodic, repetitive connection pattern.
What it is
The practice of detecting command-and-control by looking for the repetitive, roughly periodic connections an implant makes when it checks in. Analysts examine inter-arrival times, byte-count regularity, and persistence of a destination over time.
Why it matters
Beacon analysis works even against encrypted traffic because it relies on timing and volume metadata rather than content, making it a mainstay of network-based C2 hunting.
In practice
Surfacing a hidden implant by charting flow records and finding one external host contacted every ten minutes for days, jitter notwithstanding.
What to look for
- Connections at regular intervals to the same destination.
- Consistent packet sizes in each check in.
- Activity that continues overnight and on weekends.
Common mistake
Flagging every regular connection. Updates and telemetry beacon too, so build an allow list.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
- PCAP Triage
A first pass over a capture: conversations, protocol mix, DNS, HTTP hosts and TLS names.
- Network Case
A host suspected of beaconing: work its capture from scope to beacon, then the port recall and subnet math behind it.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Wireshark Open source
Opens a capture packet by packet so you can see exactly what crossed the wire. Our notes.
-
Zeek Open source
Turns traffic into structured logs for connections, DNS, HTTP, TLS and more. Our notes.
-
Suricata Open source
An IDS that alerts on known patterns and logs protocol metadata alongside. Our notes.
-
Arkime Open source
Indexes full packet capture at scale so you can search and pull sessions later. Our notes.
Read next
- Beacon Jitter: Randomizing call-home intervals to obscure a beacon's rhythm.
- Flow Data: Summarized session metadata: who talked to whom, without payloads.
- Low and Slow: Pacing activity below thresholds to stay under the radar.