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-analysisWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package24e91357…0250b2c7
24e91357bdcd…428c0250b2c74 files · 3.4 KBScanMedium2 findings
- Executable script shipped with the skillscripts/analyst.py
- Links to outside domains
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/hunting-c2-beaconing-with-frequency-analysis@da7600a
On this page
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 8Step 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.mdfor the beacon scorer. - ATT&CK T1071 and inter-arrival timing analysis (linked in frontmatter).
Files in this version
references/11.4 KB
- api-reference.md1.4 KB
scripts/12.7 KB
- analyst.py2.7 KB
- LICENSE340 B
- SKILL.md3.2 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | Yes | Yes |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- MediumFile · Executable script shipped with the skillscripts/analyst.py
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v1.0.0 | Nov 13, 2026 | da7600a | 24e91357 | Signed | – |
More from meltedinhex
All from this publisher- writing-yara-rules-from-reversed-codemeltedinhex/writing-yara-rules-from-reversed-code4
- validating-detections-with-atomic-testsmeltedinhex/validating-detections-with-atomic-tests4
- writing-suricata-and-snort-rulesmeltedinhex/writing-suricata-and-snort-rules3
- writing-sigma-detection-rulesmeltedinhex/writing-sigma-detection-rules3
More in DFIR and threat hunting
See the category- hunting-for-command-and-control-beaconingmukul975/hunting-for-command-and-control-beaconing5
- audit-context-buildingtrailofbits/audit-context-building4
- incident-response-forensicssecurityskills/incident-response-forensics3
- extracting-credentials-from-memory-dumpmukul975/extracting-credentials-from-memory-dump3
- analyzing-browser-forensics-with-hindsightmukul975/analyzing-browser-forensics-with-hindsight3
- forensics-ctfaeondave/forensics-ctf3
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login