CyberKit

Beaconing

Malware 'phoning home' on a regular interval.

What it is

Beaconing is the periodic check-in traffic from a compromised host to its command-and-control server, asking for instructions. It often follows a regular interval, sometimes with jitter to look less robotic.

Why it matters

That rhythmic pattern is a reliable network detection opportunity, spotting regular, low-volume callbacks can surface an implant even when the payload itself is unknown.

In practice

A host contacting the same domain every 60 seconds (±10% jitter): a textbook beacon.

What to look for

  • Connections to the same host at a steady interval, with small jitter.
  • Small, similar request and response sizes.
  • Activity that continues outside working hours.

Common mistake

Flagging every regular connection. Update checks and telemetry beacon too; baseline the host before calling it C2.

Use it in CyberKit

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.

ATT&CK techniques

Read next

Sources