hunting-domain-fronting-and-cdn-abuse
Hunts for domain fronting and CDN abuse by detecting TLS SNI versus HTTP Host header
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-domain-fronting-and-cdn-abuseWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package3e014a60…d418f180
3e014a601ca1…db6bd418f1804 files · 2.9 KBScanMedium2 findings
- Executable script shipped with the skillscripts/analyst.py
- Links to outside domains
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/hunting-domain-fronting-and-cdn-abuse@da7600a
On this page
When to Use
- You have TLS/HTTP telemetry (Zeek ssl.log + http.log, proxy logs) and want to detect domain fronting, where the TLS SNI shows a benign CDN domain but the inner HTTP Host differs.
- You are hunting C2 hidden behind high-reputation CDNs.
Do not use SNI/Host mismatch as definitive — some legitimate setups differ. Corroborate with destination behavior and reputation.
Prerequisites
- Telemetry pairing TLS SNI with the inner HTTP Host (or proxy logs exposing both).
Workflow
Step 1: Detect SNI/Host mismatch
python scripts/analyst.py hunt flows.csvFlags connections where the TLS SNI and HTTP Host headers resolve to different registered domains, especially when the SNI is a known CDN/fronting-capable domain.
Step 2: Surface CDN-hosted anomalies
Highlight high-reputation CDN SNIs carrying long-lived or beaconing flows.
Step 3: Confirm
Corroborate with beacon periodicity, JA3, and destination reputation; many CDN mismatches are benign.
Step 4: Operationalize
Write a detection for SNI/Host registered-domain mismatch on fronting-capable CDNs.
Validation
- Mismatch is computed on the registered domain, not the full hostname.
- Known CDN SNIs are recognized to prioritize fronting-capable cases.
- Findings are presented with corroboration needs, not as proof.
Pitfalls
- Legitimate multi-tenant CDN/edge configs producing benign mismatches.
- Encrypted SNI (ECH) hiding the SNI entirely — different hunt required.
- Treating any CDN traffic as suspicious (high false-positive rate).
References
- See
references/api-reference.mdfor the hunter. - ATT&CK T1090.004 and the TLS SNI RFC (linked in frontmatter).
Files in this version
references/11.1 KB
- api-reference.md1.1 KB
scripts/12.7 KB
- analyst.py2.7 KB
- LICENSE340 B
- SKILL.md2.5 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 | 3e014a60 | 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