Windows Chromium-Based Browser Launched With --load-extension Flag

Alerts when a Chromium-based browser starts with --load-extension= to load a custom extension.

FreeReviewedSigma · Medium · v2
Product
windows
Category
process_creation
Author
Aedan Russell, frack113, X__Junior (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-06-19
Updated
2026-07-31

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 flags process creation where a Chromium-based browser (Chrome, Edge, Brave, Opera, or Vivaldi) is executed with a command line containing the --load-extension= flag. Attackers can use this behavior to force the browser to load attacker-controlled extensions at runtime, which may enable persistence or data access. The detection relies on Windows process creation telemetry capturing the image path and full command line.

Related detections9 linkedT1176 — drag to rearrange
Windows: Chromium-Based Browser Launched via Script Host with --load-extension
Suspicious Browser Launch with Unpacked Extension Loaded via load-extension (via process_creation)
Malicious GenAI Browser Extension C2 and PAC Redirection (via proxy)
Suspicious Microsoft Edge Headless Launch with Unpacked Extension via SNOWBELT (via process_creation)
Suspicious Browser Extension Force-Install via Registry (via registry_set)
Suspicious Microsoft Edge Native Messaging Host Registration via UNC6692
Malicious Madgicx Plus Chrome Extension Identifiers on Disk
Suspicious Browser Extension Sideload From a User Path (via process_creation)
Suspicious Chrome Remote Debugging Port for Browser Session Theft
Windows Chromium-Based Browser Launched With --load-extension Flag
Pivot detection · T1176 · 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.