Suspicious Chrome Remote Debugging Port for Browser Session Theft

PremiumReviewedSigma · Medium · v1
Product
macos
Category
process_creation
Author
HuntRule
Published
2026-08-11
Updated
2026-08-28

ATT&CK techniques

Persistence
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects a Chromium based browser being started with a remote debugging port enabled, which exposes a local DevTools protocol endpoint an attacker can drive to read cookies and session data. XCSSET v4.0 launches Chrome with CDP on a local port to hijack authenticated browser sessions. Detecting the debugging port surfaces browser session theft staged through the debugging interface.

Related detections8 linkedT1176 — drag to rearrange
Suspicious Browser Extension Sideload From a User Path (via process_creation)
Suspicious Microsoft Edge Unpacked Extension Load via UNC6692 Edgecution
Malicious Chrome Extension Sideload via --load-extension from User-Writable Path (via process_creation)
Suspicious Edgecution Malicious Extension Load via Headless Edge (via process_creation)
Malicious Chrome Relaunch Hijack by FlutterShell Backdoor on macOS (via process_creation)
Windows: Chromium-Based Browser Launched via Script Host with --load-extension
Windows Chromium-Based Browser Launched With --load-extension Flag
Windows ChromeLoader Execution via Scheduled Task and Hidden PowerShell Launch
Suspicious Chrome Remote Debugging Port for Browser Session Theft
Pivot detection · T1176 · 8 related

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