Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
meltedinhex/hunting-c2-beaconing-with-frequency-analysisDFIR and threat hunting

hunting-c2-beaconing-with-frequency-analysis

⁨Detects command-and-control beacons in network logs by analyzing connection⁩

v1.0.03 installs+3 in 7 days24 StarsApache-2.0synced 10 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install meltedinhex/hunting-c2-beaconing-with-frequency-analysis

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
f2YORqFRt6…Kyb7zFDA==The CLI checks the SHA-256 and the signature before it writes a file.
Package24e91357…0250b2c7
24e91357bdcd…428c0250b2c74 files · ⁦3.4 KB⁩
ScanMedium2 findings
  • Executable script shipped with the skillscripts/analyst.py
  • Links to outside domains
See the full scan
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/hunting-c2-beaconing-with-frequency-analysis@da7600a

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.

bash
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

  • See references/api-reference.md for the beacon scorer.
  • ATT&CK T1071 and inter-arrival timing analysis (linked in frontmatter).

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumFile · Executable script shipped with the skillscripts/analyst.py
  2. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v1.0.0Nov 13, 2026da7600a24e91357Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login