hunting-for-cobalt-strike-beacons
Detect Cobalt Strike beacon network activity with specialized fingerprinting and analysis.
Install
mkdir -p .claude/skills/hunting-for-cobalt-strike-beacons && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11207" && unzip -o skill.zip -d .claude/skills/hunting-for-cobalt-strike-beacons && rm skill.zipInstalls to .claude/skills/hunting-for-cobalt-strike-beacons
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Detect Cobalt Strike beacon network activity using default TLS certificateKey capabilities
- →Detect Cobalt Strike beacon activity
- →Analyze TLS certificates
- →Match HTTP C2 profiles
- →Score beacon confidence
How it works
It correlates TLS fingerprints, interval jitter, and HTTP patterns to identify Cobalt Strike beacon callbacks.
Inputs & outputs
When to use hunting-for-cobalt-strike-beacons
- →Hunt for Cobalt Strike traffic
- →Analyze network logs for C2
- →Validate monitoring coverage
- →Detect beacon activity patterns
About this skill
Hunting for Cobalt Strike Beacons
Overview
Cobalt Strike is the most prevalent command-and-control framework used by both red teams and threat actors. Beacon, its primary payload, communicates with team servers using configurable HTTP/HTTPS/DNS profiles that can mimic legitimate traffic. However, default configurations and behavioral patterns remain detectable through TLS certificate analysis (default serial 8BB00EE), JA3/JA3S fingerprinting, beacon interval jitter analysis, and HTTP malleable profile pattern matching. This skill covers building detection capabilities using Zeek network logs, Suricata IDS rules, and Python-based PCAP analysis to identify beacon callbacks in network traffic.
When to Use
- When investigating security incidents that require hunting for cobalt strike beacons
- When building detection rules or threat hunting queries for this domain
- When SOC analysts need structured procedures for this analysis type
- When validating security monitoring coverage for related attack techniques
Prerequisites
- Zeek 6.0+ with JA3 and HASSH packages installed
- Suricata 7.0+ with Emerging Threats ruleset
- Python 3.9+ with scapy and dpkt libraries
- Network traffic captures (PCAP) or live Zeek logs
- RITA (Real Intelligence Threat Analytics) for beacon scoring
- Threat intelligence feeds with known Cobalt Strike IOCs
Steps
Step 1: TLS Certificate Analysis
Detect default Cobalt Strike certificates using JA3S fingerprints, certificate serial numbers, and JARM fingerprints in Zeek ssl.log.
Step 2: Beacon Interval Analysis
Analyze connection timing patterns to identify regular callback intervals with configurable jitter, characteristic of beacon behavior.
Step 3: HTTP Profile Detection
Match HTTP request patterns (URI paths, headers, user-agents) against known malleable C2 profiles.
Step 4: Correlate and Score
Combine multiple indicators (TLS + timing + HTTP profile) into a composite beacon confidence score.
Expected Output
JSON report containing detected beacon candidates with confidence scores, TLS fingerprints, timing analysis, HTTP profile matches, and recommended response actions.
When not to use it
- →When network logs are unavailable
- →General malware analysis
Prerequisites
Limitations
- →Requires specific network monitoring tools
- →Beacon profiles can be customized to evade detection
How it compares
It combines multiple network indicators into a composite confidence score rather than relying on single IOCs.
Compared to similar skills
hunting-for-cobalt-strike-beacons side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| hunting-for-cobalt-strike-beacons (this skill) | 0 | 2mo | Review | Advanced |
| sentry-data-handling | 0 | 27d | Caution | Advanced |
| openrouter-audit-logging | 1 | 27d | Caution | Intermediate |
| klingai-audit-logging | 1 | 27d | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by mukul975
View all by mukul975 →You might also like
sentry-data-handling
jeremylongshore
Manage sensitive data properly in Sentry. Use when configuring PII scrubbing, data retention, GDPR compliance, or data security settings. Trigger with phrases like "sentry pii", "sentry gdpr", "sentry data privacy", "scrub sensitive data sentry".
openrouter-audit-logging
jeremylongshore
Implement audit logging for OpenRouter compliance. Use when meeting regulatory requirements or security audits. Trigger with phrases like 'openrouter audit', 'openrouter compliance log', 'openrouter security log', 'audit trail'.
klingai-audit-logging
jeremylongshore
Implement comprehensive audit logging for Kling AI operations. Use when tracking API usage, compliance requirements, or security audits. Trigger with phrases like 'klingai audit', 'kling ai logging', 'klingai compliance log', 'video generation audit trail'.
vertex-engine-inspector
jeremylongshore
Execute inspect and validate Vertex AI Agent Engine deployments including Code Execution Sandbox, Memory Bank, A2A protocol compliance, and security posture. Generates production readiness scores. Use when asked to "inspect agent engine" or "validate depl... Trigger with relevant phrases based on skill purpose.
sentry-multi-env-setup
jeremylongshore
Configure Sentry across multiple environments. Use when setting up Sentry for dev/staging/production, managing environment-specific configurations, or isolating data. Trigger with phrases like "sentry environments", "sentry staging setup", "multi-environment sentry", "sentry dev vs prod".
ci
PioneersHub
Run the local CI pipeline (ruff, bandit, pytest, sonar-scanner) and refresh SonarQube.