Suspicious Chrome Launched With Remote Debugging Port For Cookie Theft

PremiumReviewedSigma · High · 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 chrome.exe started with a remote debugging port argument which MaaS infostealers use to attach over the DevTools protocol and read decrypted cookies and session tokens after Chrome application-bound encryption defenses. Adversaries drive a debug-enabled browser instance to harvest authenticated session material without triggering the standard credential prompts.

Related detections9 linkedT1555.003 — drag to rearrange
Malicious RemusStealer Credential Exfiltration to pics TLD C2
Suspicious Access to Chrome Login Data on macOS (via process_creation)
Suspicious Access To Chrome Credential Files
Windows SQLite CLI Querying Chromium Browser Profile Databases
Suspicious Access To Chrome Elevation Service COM Object via Katz Stealer
Suspicious Data Exfiltration Channel to Telegram or Discord via dns_query
Suspicious 1Phish Kit Cookies and Telemetry Beacon
Suspicious AiTM Session Cookie Exfiltration to log_cookie Endpoint
Suspicious Named Pipe ChromeDecryptIPC Used by Stealer (via pipe_created)
Suspicious Chrome Launched With Remote Debugging Port For Cookie 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.