Possible Cobalt Strike Beacon via Default Malleable Profile URIs

PremiumReviewedSigma · Medium · v1
Category
proxy
Author
HuntRule
Published
2026-09-27
Updated
2026-09-27

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 HTTP requests to the /dpixel and /submit.php URIs which correspond to default Cobalt Strike Malleable C2 profile paths observed in the ColunmTK APT41 intrusions. The GET and POST traffic carries encoded beacon check-ins and task results. Detecting these paths surfaces command and control that operators forgot to customize.

Related detections9 linkedT1071.001 — drag to rearrange
Possible GoldFactory GoldPickaxe Mobile Trojan C2 API Calls
Malicious Phishing Data Exfiltration to SheetBest API by GitBait Campaign (via proxy)
Suspicious Telegram Bot API getUpdates Polling for C2 by Millenium RAT (via proxy)
Possible Telegram Bot API Command and Control Traffic
Possible Lazarus C2 Beacon to Uncommon Port 1224 Loader Endpoints
Possible Godfather Android Banking Trojan C2 Endpoints
Possible EndRAT C2 Communication via Distinctive Client Identifier
Suspicious Creation of MuddyWater Log-Named Payload Files
Possible FDMTP Implant C2 Cluster Registration via HTTP (via proxy)
Possible Cobalt Strike Beacon via Default Malleable Profile URIs
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.