Skip to content

meltedinhex/analyst-ai-pack / skills/hunting-c2-beaconing-with-frequency-analysis

hunting-c2-beaconing-with-frequency-analysis

Verified

Detects command-and-control beacons in network logs by analyzing connection timing: measuring inter-arrival intervals, accounting for jitter, and scoring regularity per source/destination pair to surface periodic callbacks. Activates for requests to hunt C2 beaconing, find periodic callbacks, or analyze connection-interval regularity.

Hunting C2 Beaconing with Frequency Analysis

When to Use

  • You have connection logs (proxy, firewall, Zeek/conn.log, NetFlow) and want to find implants that call home on a schedule.
  • You are testing a hypothesis that a beacon is hiding in normal-looking web traffic.
  • You need to rank source→destination pairs by timing regularity, allowing for jitter.

Do not use pure interval regularity as a verdict — software update checks, telemetry, and keep-alives also beacon; combine timing with destination reputation and data volume.

Prerequisites

  • Connection records with timestamp, source, destination (IP/domain), and ideally bytes, over a window long enough to capture many callbacks (hours to days).
  • A way to enrich destinations (reputation, age, rarity) for follow-up.

Workflow

Step 1: Group and order by pair

Bucket connections by (source, destination) and sort timestamps. Require a minimum count so the interval statistics are meaningful.

Step 2: Compute inter-arrival intervals

Derive deltas between consecutive connections per pair; the interval distribution reveals periodicity.

Step 3: Score regularity with jitter tolerance

A low coefficient of variation (std/mean) of intervals indicates a steady beacon; modern beacons add jitter, so score on tolerance rather than requiring identical intervals.

python scripts/analyst.py beacon conn.json --min-events 8

Step 4: Reduce false positives

Down-rank known update/telemetry destinations and CDNs; up-rank rare/young domains, small fixed payload sizes, and odd ports.

Step 5: Triage and confirm

For top pairs, pull payloads/JA3, destination intel, and host context; confirm via the C2/beacon config skills and escalate.

Validation

  • Top candidates show consistently spaced callbacks (low CV) over many events, not a handful.
  • Known-benign periodic services are filtered or explained.
  • Confirmed beacons corroborate with destination reputation or payload analysis.

Pitfalls

  • Too few events per pair, making the interval statistics noise.
  • Requiring perfect periodicity and missing jittered beacons.
  • Ignoring data-volume regularity, a strong secondary beacon signal.

References

slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall