Windows Chromium Process Loaded Extension via Command-Line
The following analytic detects instances where Google Chrome is started with the --load-extension command-line flag, which allows loading unpacked or non-standard extensions. This behavior can indicate attempts to…
Description
The following analytic detects instances where Google Chrome is started with the --load-extension command-line flag, which allows loading unpacked or non-standard extensions. This behavior can indicate attempts to bypass enterprise extension policies, install malicious extensions, or load potentially harmful browser components. Monitoring such activity helps identify unauthorized extension usage, potential malware persistence mechanisms, or policy violations that could compromise browser security.
Detection logic
Detection requirements
- Platform
- Windows
The rule states no platform. This is derived from the ATT&CK technique it maps to.
- Log source category
- crowdstrike_processrollup2sysmon_eventid_1windows_event_log_security_4688
Known benign triggers
- Developers or IT admins loading unpacked extensions for testing or deployment purposes.
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| peter.sh/experiments/chromium-command-line-switches/ | 6 |
| www.gdatasoftware.com/blog/2025/11/38298-learning-about-browser-hijacking | 4 |
From the source
- At source
- Open at source
- Upstream identifier
- 1b8a468a-52e3-4206-b14a-73165441684c
- Tagged by the source as
- Browser HijackingEndpointendpointSplunk CloudSplunk EnterpriseSplunk Enterprise Securityendpoint
Licence
- Published under
- Apache License 2.0Read the licence
- Attribution
- Required
- Obtained under
- Apache-2.0Read the origin licence
Authorship
- Written by
- Published
- Aug 26, 2026
- Version
- 1