hunting-c2-beaconing-with-frequency-analysis
Detects command-and-control beacons in network logs by analyzing connection
v1.0.03 instalações+3 em 7 dias24 EstrelasApache-2.0sincronizado há 10 horas
Instalar
Ainda não tem a CLI da NotHoly? Instale primeiro.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install meltedinhex/hunting-c2-beaconing-with-frequency-analysisGrava em ~/.notholy/skills depois de conferir a assinatura e o SHA-256.
AssinaturaAssinado, ed25519
Pacote24e91357…0250b2c7
24e91357bdcd…428c0250b2c74 arquivos · 3.4 KBVarreduraMédio2 achados
- Script executável junto com a skillscripts/analyst.py
- Links para domínios externos
Fontegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/hunting-c2-beaconing-with-frequency-analysis@da7600a
Este item ainda não foi escrito no seu idioma, então aparece em English.
Nesta página
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).
Arquivos desta versão
references/11.4 KB
- api-reference.md1.4 KB
scripts/12.7 KB
- analyst.py2.7 KB
- LICENSE340 B
- SKILL.md3.2 KB
Permissões
| Permissão | Declarada | Encontrada na varredura |
|---|---|---|
| Lê arquivos | Não | Não |
| Grava arquivos | Não | Não |
| Roda comandos no shell | Sim | Sim |
| Usa a rede | Sim | Sim |
| Usa conectores | Não | Não |
| Controla um navegador | Não | Não |
Achados da varredura
Revisado em 13 de nov. de 2026
- MédiaArquivo · Script executável junto com a skillscripts/analyst.py
- InfoLink · Links para domínios externos
Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.
| Versão | Publicada em | Commit | SHA-256 | Assinatura | Mudança de permissão |
|---|---|---|---|---|---|
| v1.0.0 | 13 de nov. de 2026 | da7600a | 24e91357 | Assinada | – |
Mais de meltedinhex
Tudo deste publicador- 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
Mais em DFIR e threat hunting
Ver a categoria- 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
Pergunte tudo o que o seu escopo permite.
Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.
- 1/3
Crie a conta
Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.
Pessoa físicaEmpresa - 2/3
Adicione créditos
No cartão. Você paga por token, sem assinatura.
$5.00recarga mínima - 3/3
Pergunte
No chat, ou instale o CLI e rode notholy login no terminal.
$ notholy login