Possible FDMTP Implant C2 Cluster Registration via HTTP (via proxy)

PremiumReviewedSigma · High · v1
Category
proxy
Author
HuntRule
Published
2026-09-25
Updated
2026-09-25

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 the QuickFox FDMTP implant contacting its command and control cluster using a distinctive registration request. The implant issues a GetCluster request carrying the DotNet-TcpFDMTP protocol tag to obtain live C2 nodes. This URI pattern is unique to the FDMTP framework.

Related detections9 linkedT1071.001 — drag to rearrange
Possible EndRAT C2 Communication via Distinctive Client Identifier
Suspicious Creation of MuddyWater Log-Named Payload Files
Possible SPECTRALVIPER C2 Communication via Crafted Consent Cookie Values
Malicious Winter Vivern C2 Endpoint saveMessage via Proxy (via proxy)
Suspicious Whisper Backdoor Log File in Windows Temp
Suspicious Lunar Backdoor State File Creation via File System
Malicious OilRig OAuth Application Sign-In via Azure (via azure)
Malicious FIN7 DiceLoader C2 via Placeholder User-Agent (via proxy)
Malicious D3f@ck Loader C2 via Java User-Agent Ready Beacon (via proxy)
Possible FDMTP Implant C2 Cluster Registration via HTTP (via proxy)
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.