Windows Chromium Process Loaded Extension via Command-Line
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.
Query · spl
| tstats `security_content_summariesonly` min(_time) as firstTime max(_time) as lastTime from datamodel=Endpoint.Processes where Processes.process_name = "Chrome.exe" Processes.process= "*--load-extension*" by Processes.action Processes.dest Processes.original_file_name Processes.parent_process Processes.parent_process_exec Processes.parent_process_guid Processes.parent_process_id Processes.parent_process_name Processes.parent_process_path Processes.process Processes.process_exec Processes.process_guid Processes.process_hash Processes.process_id Processes.process_integrity_level Processes.process_name Processes.process_path Processes.user Processes.user_id Processes.vendor_product | `drop_dm_object_name(Processes)` | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)` | `windows_chromium_process_loaded_extension_via_command_line_filter`
Implementation guide
To successfully implement this search you need to be ingesting information
on process that include the name of the process responsible for the changes from
your endpoints into the Endpoint datamodel in the Processes node. In addition,
confirm the latest CIM App 4.20 or higher is installed and the latest TA for the
endpoint product.
Known false positives
- Developers or IT admins loading unpacked extensions for testing or deployment purposes.
Analyst notes
Known false positives: Developers or IT admins loading unpacked extensions for testing or deployment purposes.