Suspicious ctfmon.exe Network Connection to PikaBot C2 Ports

PremiumReviewedSigma · High · v1
Product
windows
Category
network_connection
Author
HuntRule
Published
2026-10-25
Updated
2026-10-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 injected ctfmon.exe process establishing outbound connections to uncommon high ports used by PikaBot command and control such as 2078, 2083, 2222 and the 13720-13786 range. Because ctfmon.exe never initiates network traffic legitimately, any such connection indicates the malware beacon operating from hijacked memory. This helps surface active C2 that evaded process based detection.

Related detections9 linkedT1071.001 — drag to rearrange
Malicious AddInProcess32 Network Beacon on PureRAT C2 Ports
Malicious Data Exfiltration via curl with Stealer Specific BuildID Header
Suspicious Shadow File Exfiltration Over Dev TCP on Linux via Process Creation (via process_creation)
Suspicious Netcat Reverse Shell via Named Pipe on Linux via Process Creation (via process_creation)
Malicious GenAI Browser Extension C2 and PAC Redirection (via proxy)
Possible Prometei Botnet C2 URI Pattern
Malicious PUBLOAD Fake Windows Update C2 Request via Proxy (via proxy)
Possible Lampion C2 Beacon With dados Parameter
Suspicious Non-Standard HTTP Methods Used for Covert C2 (via proxy)
Suspicious ctfmon.exe Network Connection to PikaBot C2 Ports
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.