Browse Rules

Search and filter across all detection sources

11 rules

panther medium python

OSQuery Detected Unwanted Chrome Extensions

Monitor for chrome extensions that could lead to a credential compromise.

elastic-protections high eql

Suspicious Browser Preferences File Modification

Identifies the modification of commonly used browsers settings via Preferences change. Adversaries may install a rogue browser extension or disable certain browser hardening settings to maintain persistence or evade restrictions.

elastic-protections high eql

Suspicious Browser Preference File Modification

Detects modification of browser preference files by suspicious processes like scripts or untrusted binaries. Threat actors modify these files to establish persistence and control browser extensions.

elastic-protections high eql

Suspicious Browser Files Modification

Identifies the modification of commonly used browsers settings via file or registry change. Adversaries may install a rogue browser extension or disable certain browser hardening settings to maintain persistence or evade restrictions.

elastic low eql

Browser Extension Install

Identifies the install of browser extensions. Malicious browser extensions can be installed via app store downloads masquerading as legitimate extensions, social engineering, or by an adversary that has already compromised a system.

splunk unknown spl

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 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 securit

elastic high eql

Manual Loading of a Suspicious Chromium Extension

Detects the manual loading of a Chromium-based browser extension via command line arguments. This activity is suspicious and could indicate a threat actor loading a malicious extension to persist or collect browsing secrets such as cookies and authentication tokens.

splunk unknown spl

Windows Chrome Enable Extension Loading via Command-Line

The following analytic detects instances where Google Chrome is started with the --disable-features=DisableLoadExtensionCommandLineSwitch flag, effectively enabling the loading of extensions via the command line. This may indicate attempts to bypass enterprise extension policies, load unauthorized or malicious extensions, or manipulate browser behavior. Monitoring this activity helps identify potential security policy violations, malware persistence techniques, or other suspicious Chrome modific

splunk unknown spl

Windows Native Messaging Host Registered By User Writable Binary

The following analytic detects a binary running from a user-writable or Windows directory (C:\Users, C:\ProgramData, C:\PerfLogs or C:\Windows) that creates or modifies a Chrome or Edge NativeMessagingHosts registry key. This activity is significant because registering a native messaging host manifest lets a malicious browser extension launch arbitrary local programs, which has been abused for command and control and persistence. If confirmed malicious, an attacker could execute code through the

splunk unknown spl

Windows Native Messaging Host Spawns User Writable Process

The following analytic detects a process located in a user-writable directory (C:\Users, C:\ProgramData or C:\PerfLogs) that is spawned by cmd.exe acting as a Chromium native messaging host launcher. This activity is significant because attackers register a malicious native messaging host so that a browser extension can run batch scripts and binaries such as a bundled Python interpreter on demand, giving them a stealthy command and control and persistence channel. If confirmed malicious, this co

elastic high kql

Multiple Credential Access by VS Code or Cursor IDE Descendant

Detects a process descended from Visual Studio Code or Cursor opening at least two distinct sensitive files, such as browser credential stores, cloud tokens, or SSH and package-manager secrets. Malicious IDE extensions use the editor process tree to harvest more than one credential store in a single session.