Suspicious Browser Launch With Remote Debugging Port via Process Creation

PremiumReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-07-26
Updated
2026-08-28

ATT&CK techniques

Collection → 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. Exfiltration

  12. Impact

What it detects

This rule detects a Chromium-based browser started with the remote debugging port switch, the Chrome DevTools Protocol abuse msaRAT uses to hijack the browser and build a covert C2 channel as reported by Cisco Talos. The loader spawns the browser under its control to drive WebRTC and DevTools traffic through the victim session. Detecting the remote debugging switch surfaces browser hijacking that blends into normal web activity.

Related detections9 linkedT1071.001 — drag to rearrange
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)
Malicious Splinter Post-Exploitation Implant C2 URI Pattern (via proxy)
Suspicious Browser Launch With Remote Debugging Port via Process Creation
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.