Individual skill

hunting-for-beaconing-with-frequency-analysis

Identify command-and-control beaconing patterns in network traffic by applying statistical frequency analysis, jitter calculation, and coefficient of variation scoring to detect periodic callbacks from compromised endpoints.

internal/tools/skills/data/threat-hunting/hunting-for-beaconing-with-frequency-analysis/SKILL.md

Read pinned source

Source commit d42f381ad34843e71a42658e5c57290c713e85af

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,313
Repository last updated
Nov 7, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Hunting for Beaconing with Frequency Analysis

## When to Use

- When proactively searching for compromised endpoints calling back to C2 infrastructure
- After threat intelligence reports indicate active C2 frameworks targeting your sector
- When network logs show periodic outbound connections to unfamiliar destinations
- During purple team exercises validating C2 detection capabilities
- When investigating a potential breach and need to identify active C2 channels

## Detection Gaps & Validation

- **High jitter defeats CV thresholds:** a `CV < 0.20` rule misses beacons configured with large jitter (Cobalt Strike `jitter 50`, or Sunburst's minutes-scale randomization) — widen the window, score on data-size consistency, and use FFT/autocorrelation rather than CV alone for jittered beacons.
- **Long sleep / dormancy:** beacons sleeping hours-to-days produce too few connections in a 24h window to be significant — extend the lookback to 7–14 days and lower the `min connections` floor for rare destinations.