Suspicious Chrome Launch with Remote Debugging for Credential Theft

PremiumReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-09-18
Updated
2026-09-18

ATT&CK techniques

Cred Access
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects a Chromium-based browser launched with a remote debugging port or pipe argument, a technique used by EddieStealer and similar infostealers to drive the browser over the DevTools protocol and extract saved passwords and cookies. Remote debugging flags are rarely set by end users and indicate automated browser credential theft.

Related detections9 linkedT1555.003 — drag to rearrange
Suspicious Access To Chrome Elevation Service COM Object via Katz Stealer
Suspicious Chrome Launched With Remote Debugging Port For Cookie Theft
Suspicious Data Exfiltration Channel to Telegram or Discord via dns_query
Suspicious Named Pipe ChromeDecryptIPC Used by Stealer (via pipe_created)
Suspicious Clipboard Data Access via Get-Clipboard (BeaverTail OtterCookie)
Malicious Edge Credential Parser Execution via PowerShell (via process_creation)
SapphireStealer Working Directory File Drop in Temp
Malicious RemusStealer Credential Exfiltration to pics TLD C2
Suspicious Local Password Validation via dscl authonly
Suspicious Chrome Launch with Remote Debugging for Credential Theft
Pivot detection · T1555.003 · 9 related

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