Windows Chromium-Based Browsers Launched with Headless Debugging and User Profile Directory

Alerts on Windows launches of Chromium-based browsers in headless + remote debugging mode targeting a user data directory.

FreeReviewedSigma · High · v2
Product
windows
Category
process_creation
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-12-23
Updated
2026-07-31

ATT&CK techniques

Defense Evasion → Collection
  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. C2

  12. Exfiltration

  13. Impact

What it detects

This rule identifies Windows process executions where a Chromium-based browser is started with headless mode and remote debugging enabled while also specifying a user data directory. Attackers can use these flags to automate browser access, persist session data under a chosen profile, and potentially enable data collection or remote control behavior. It relies on process creation telemetry with command-line arguments containing the remote debugging, headless, and user data directory switches.

Related detections9 linkedT1564.003 — drag to rearrange
Suspicious Browser Launch With Remote Debugging Port via Process Creation
Conhost Suspicious Command Execution
Suspicious conhost Headless Execution for Hidden Window
Windows cmd.exe Executing start Utility with Hidden Window Flags (/b or /min)
PowerShell Launch With --headless From Conhost.exe on Windows
Windows: Headless Chromium Browser Execution via --headless
Windows Browser Launched with Remote Debugging Flags
Windows PUA AdvancedRun.exe Execution
Windows Process Creation: Headless Chromium Download via dump-dom
Windows Chromium-Based Browsers Launched with Headless Debugging and User Profile Directory
Pivot detection · T1564.003 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

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