CyberKit

Beacon Jitter

Also called jitter, sleep jitter.

Randomizing call-home intervals to obscure a beacon's rhythm.

What it is

A deliberate randomization applied to the interval between an implant's check-ins, so the call-home timing varies around a base value instead of landing on a fixed clock. Operators set jitter as a percentage of the sleep time.

Why it matters

Jitter is meant to defeat naive detections that look for perfectly periodic traffic, so analysts compensate by examining the distribution of intervals over long windows rather than expecting a clean beat.

In practice

Still spotting a beacon despite heavy jitter, because clustering its call-home timestamps revealed a consistent underlying interval.

What to look for

  • Intervals that cluster around a value with some spread.
  • Regular connections that never quite line up.
  • Sleep values recovered from the implant config.

Common mistake

Looking for perfect timing only. Jitter adds randomness, so look for clusters, not exact repeats.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice 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 Analysis: Finding C2 callbacks by their periodic, repetitive connection pattern.
  • Malleable C2 Profile: A config that reshapes C2 traffic to mimic benign protocols.
  • Low and Slow: Pacing activity below thresholds to stay under the radar.

Sources