Possible Cobalt Strike Beacon URI Pattern via Web C2

PremiumReviewedSigma · Medium · v1
Category
proxy
Author
HuntRule
Published
2026-10-16
Updated
2026-10-16

ATT&CK techniques

C2
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. Exfiltration

  13. Impact

What it detects

This rule detects outbound HTTP requests to Cobalt Strike malleable profile URIs observed in Blister post-exploitation traffic, including the /safebrowsing/ and /rest/2/meetings beacon paths often paired with Fastly domain fronting. These structured C2 URIs indicate beaconing to an attacker-controlled team server masquerading as benign web services.

Related detections9 linkedT1071.001 — drag to rearrange
Malicious Dropbox Cloud C2 via Spoofed Googlebot User Agent
Possible FluBot C2 Polling via Known Malware URI Paths
Malicious MetaStealer C2 via cpp-httplib User-Agent (via proxy)
Malicious SharkBot Android Banking Trojan C2 via DGA Domain Suffix
Possible Team9 C2 via Emercoin bazar Domain Resolution
Suspicious Diamond Sleet Anomalous Microsoft Internet Explorer User Agent (via proxy)
Suspicious Diamond Sleet C2 via LambLoad Addon PHP URI Pattern (via proxy)
Malicious Sapphire Sleet curl to osascript Chain With mac-cur User-Agent (via process_creation)
Malicious Marbled Dust Backdoor Executing from Public Videos Directory
Possible Cobalt Strike Beacon URI Pattern via Web C2
Pivot detection · T1071.001 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.