hunting-cobalt-strike-traffic
Hunts for Cobalt Strike beacon traffic by detecting default stager URI checksum8
v1.0.02 installs+2 in 7 days24 StarsApache-2.0synced 11 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install meltedinhex/hunting-cobalt-strike-trafficWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package6d440cde…b24023cf
6d440cdefb9d…29c5b24023cf4 files · 3.3 KBScanMedium2 findings
- Executable script shipped with the skillscripts/analyst.py
- Links to outside domains
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/hunting-cobalt-strike-traffic@da7600a
On this page
When to Use
- You have HTTP request logs (proxy/Zeek http.log) and/or process telemetry and want to detect default-configuration Cobalt Strike beacons.
- You are triaging suspected C2 using known default artifacts before deeper analysis.
Do not use default-indicator detection as proof — operators customize Malleable C2 profiles. Absence of defaults does not mean no Cobalt Strike. This skill parses telemetry and executes nothing.
Prerequisites
- HTTP request URIs and/or process/pipe telemetry.
Workflow
Step 1: Detect default stager URIs
python scripts/analyst.py hunt http.csvFlags request URIs whose path matches the Cobalt Strike default stager checksum8 algorithm (sum of the path characters mod 256 equals 92 for x86 or 93 for x64 stagers).
Step 2: Match default profile artifacts
Flag default user-agents, default URIs (/__utm.gif, /submit.php, /pixel), and default named
pipes (\\.\pipe\msagent_*, \\.\pipe\status_*) when present in telemetry.
Step 3: Confirm
Corroborate with beaconing periodicity and destination reputation; pivot to memory/config analysis.
Step 4: Operationalize
Write detections for checksum8 URIs and known default artifacts, accepting they catch defaults only.
Validation
- checksum8 detection correctly computes the path-character sum mod 256.
- Default profile artifacts are matched exactly, not by loose substrings.
- Findings are presented as default-indicator hits, not definitive attribution.
Pitfalls
- Customized Malleable C2 profiles defeating all default-artifact checks.
- checksum8 false positives on unrelated short URIs — corroborate with other signals.
- Treating a single default hit as confirmation without behavioral corroboration.
References
- See
references/api-reference.mdfor the hunter. - ATT&CK S0154 Cobalt Strike (linked in frontmatter).
Files in this version
references/11.3 KB
- api-reference.md1.3 KB
scripts/13.5 KB
- analyst.py3.5 KB
- LICENSE340 B
- SKILL.md2.7 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 | 6d440cde | 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