hunting-for-command-and-control-beaconing

Featured

Detect C2 beaconing patterns in network traffic using frequency analysis, jitter detection, and domain reputation to identify compromised endpoints communicating with adversary infrastructure.

AI & Automation 36,355 stars 4443 forks Updated 2 months ago Apache-2.0

Install

View on GitHub

Quality Score: 94/100

Stars 20%
100
Recency 20%
75
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Hunting for Command and Control Beaconing ## When to Use - When proactively hunting for compromised systems in the network - After threat intel indicates C2 frameworks targeting your industry - When investigating periodic outbound connections to suspicious domains - During incident response to identify active C2 channels - When DNS query logs show unusual patterns to specific domains ## Prerequisites - Network proxy/firewall logs with full URL and timing data - DNS query logs (passive DNS, DNS server logs, or Sysmon Event ID 22) - Zeek/Bro network connection logs or NetFlow data - SIEM with statistical analysis capabilities (Splunk, Elastic) - Threat intelligence feeds for domain/IP reputation ## Workflow 1. **Identify Beaconing Characteristics**: Define what constitutes beaconing (regular intervals, small payload sizes, consistent destinations, jitter patterns). 2. **Collect Network Telemetry**: Aggregate proxy logs, DNS queries, and connection metadata for analysis. 3. **Apply Frequency Analysis**: Identify connections with regular intervals using statistical methods (standard deviation, coefficient of variation). 4. **Filter Known-Good Traffic**: Exclude legitimate periodic traffic (Windows Update, AV updates, heartbeat services, NTP). 5. **Analyze Domain/IP Reputation**: Check identified beaconing destinations against threat intel, WHOIS data, and certificate transparency logs. 6. **Investigate Endpoint Context**: Correlate beaconing activity with process creation...

Details

Author
mukul975
Repository
mukul975/Anthropic-Cybersecurity-Skills
Created
8 months ago
Last Updated
2 months ago
Language
Python
License
Apache-2.0

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

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.

36,355 Updated 2 months ago
mukul975
AI & Automation Listed

detect-c2-beaconing

Detection and hunt methodology for command-and-control beaconing, where an implant calls home on a regular interval over HTTP(S), DNS, or a tunnel service, hidden inside normal egress (MITRE ATT&CK T1071 Application Layer Protocol, T1071.004 DNS, T1573 Encrypted Channel, T1571 Non-Standard Port, T1572 Protocol Tunneling, T1090 Proxy; tactic TA0011 Command and Control). Works from Zeek conn.log/ssl.log/dns.log, Suricata EVE JSON, firewall and web-proxy logs, NetFlow/IPFIX, and endpoint Sysmon Event ID 3/22. It gives the defender's view of beacon periodicity and jitter, JA3/JA3S and JA4 TLS fingerprinting, and tunnel-service detection, plus hunt steps and hardening. Use when hunting for regular callbacks, triaging a long-lived outbound connection, analyzing JA3/JA4 hashes, investigating suspected Cobalt Strike, Sliver, or Mythic C2, chasing DNS or HTTPS tunneling, or baselining egress for periodic traffic.

0 Updated 5 days ago
umbrasec-labs
AI & Automation Featured

hunting-for-cobalt-strike-beacons

Detect Cobalt Strike beacon network activity using default TLS certificate signatures (serial 8BB00EE), JA3/JA3S/JARM fingerprints, HTTP C2 profile pattern matching, beacon jitter analysis, and named pipe detection via Zeek, Suricata, and Python PCAP analysis.

36,355 Updated 2 months ago
mukul975