Potential Cookies Theft via Browser Debuggingedit

Identifies the execution of a Chromium based browser with the debugging process argument, which may indicate an attempt to steal authentication cookies. An adversary may steal web application or service session cookies and use them to gain access web applications or Internet services as an authenticated user without needing credentials.

Rule type: eql

Rule indices:

  • auditbeat-*
  • winlogbeat-*
  • logs-endpoint.events.*
  • logs-windows.*

Severity: medium

Risk score: 47

Runs every: 5 minutes

Searches indices from: now-9m (Date Math format, see also Additional look-back time)

Maximum alerts per execution: 33



  • Elastic
  • Host
  • Linux
  • Windows
  • macOS
  • Threat Detection
  • Credential Access

Version: 2 (version history)

Added (Elastic Stack release): 7.12.0

Last modified (Elastic Stack release): 8.2.0

Rule authors: Elastic

Rule license: Elastic License v2

Potential false positivesedit

Developers performing browsers plugin or extension debugging.

Investigation guideedit

## Config

If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2, events will not define `event.ingested` and default fallback for EQL rules was not added until 8.2, so you will need to add a custom pipeline to populate `event.ingested` to @timestamp for this rule to work.

Rule queryedit

process where event.type in ("start", "process_started", "info") and
process.name in ( "Microsoft Edge",
"chrome.exe", "Google Chrome", "google-
chrome-stable", "google-chrome-beta",
"google-chrome", "msedge.exe") and process.args : ("--
remote-debugging-port=*", "--remote-debugging-
targets=*", "--remote-debugging-pipe=*") and
process.args : "--user-data-dir=*" and not process.args:"--remote-

Threat mappingedit


Rule version historyedit

Version 2 (8.2.0 release)
  • Formatting only