Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
1,588 detections
Filters
Last updated
All Time
Detection languages
830
199
132
116
107
Contributors
608
289
249
88
63
Categories
20,440
11,814
5,871
5,145
4,864
1,588
Platforms
1,255
461
295
76
68
Products / Services
530
382
139
113
85
MITRE Techniques
629
565
504
437
297
CVEs
5
4
3
3
3
IDS Classtypes
5
2
2
1
IDS Protocols
5
3
2
This rule monitors for unauthorized access to the Google Chrome 'Login Data' database file by processes other than standard browser executables. It also detects the creation of known file artifacts associated with credential-stealing malware or RATs (e.g., 'chrome_logins_dump.txt' or 'gather.tar.gz'), which are indicative of credential harvesting activities.
This rule detects activities associated with the MiniBrowse tool, specifically targeting unauthorized access to browser credential stores (Login Data, Cookies) and staging files for exfiltration. Additionally, it monitors for process injection events where MiniBrowse components are injected into legitimate browser processes such as Chrome or Edge.
This rule detects potential data staging activities by monitoring for specific file paths and filenames associated with unauthorized collection of sensitive data (such as VPN configs, password databases, and office documents). It triggers when processes not typically associated with these file types access or interact with sensitive directories and file extensions.
Detects file access (open or read) events targeting documents with file paths matching known UAC-0226 Ukrainian military-themed lures. These documents are often associated with weaponized RAR archives, targeting sensitive military information such as reconnaissance platoon records or military registry data.
This rule detects unauthorized read access to sensitive credential stores (KeePass .kdbx) and VPN configuration files (OpenVPN, Cisco AnyConnect, WireGuard) by processes that are not recognized credential or VPN management software. It specifically monitors for processes exhibiting suspicious lineage, such as those spawned by PowerShell or running from the C:\ProgramData directory, which is a common technique used by attackers to hide malicious activity.
Detects malicious execution patterns during npm package installation consistent with Miasma and Mini Shai-Hulud supply chain attacks. The rule monitors for node.exe or bun.exe being spawned by npm or node-gyp that exhibit suspicious behavior, such as accessing sensitive credential paths (e.g., .ssh, .npmrc, .gitconfig) or utilizing a Phantom Gyp execution pattern where index.js is executed directly within node_modules via node-gyp, as well as bun.exe staging execution from temporary directories.
Cloud extortion group exploiting exposed credentials and storage
Detects Python interpreters (or processes executing from PyInstaller-generated temporary directories) accessing sensitive web browser files such as Login Data, Cookies, or Local State. This activity is commonly associated with information stealer malware, such as Glove Stealer, attempting to extract saved credentials from browsers.
Detects non-browser processes attempting to read, create, or modify browser-specific credential storage files (e.g., 'Login Data', 'logins.json', 'signons.sqlite') associated with Chromium-based browsers or Firefox. This activity is a common indicator of credential theft by malware such as Atlas RAT or ValleyRAT.
Detects processes attempting to load multimedia DLLs or access video capture devices that are not associated with authorized communication, media, or browser applications. This logic identifies potentially malicious attempts to capture video feeds from local cameras.
Detects instances where a Node.js process accesses, creates, or modifies sensitive files such as SSH private keys, AWS credentials, or application configuration files (.npmrc, .pypirc, .docker/config.json). This behavior is often indicative of credential theft or unauthorized configuration access by a compromised Node.js application.
This rule detects processes other than standard web browsers (Chrome, Edge, Brave) attempting to access sensitive directories within Chrome extension user data paths, such as IndexedDB, Local Storage, or Sync Data. Such activity is often indicative of credential or session cookie theft by malicious scripts or malware.
Detects node.exe accessing Chrome browser extension storage directories associated with popular cryptocurrency wallets. This activity is indicative of the Miasma/MYRA infostealer (peer-math.js) attempting to harvest encrypted wallet vaults from developer workstations, as seen in the Polymarket Trap supply chain attack.
Detects Node.js processes accessing sensitive AWS credential or configuration files. This behavior is indicative of unauthorized information gathering, often associated with infostealer malware payloads delivered via malicious npm packages.
Detects malicious activity associated with the Miasma/MYRA infostealer campaign targeting DeFi developers. The rule monitors npm lifecycle scripts (postinstall/preinstall) for suspicious execution, C2 communication with known malicious domains, unauthorized access to browser-based credential storage, and persistence attempts via LD_PRELOAD on Linux environments.
Detects Node.js or npm processes that access multiple SSH-related files within a short timeframe while also establishing external network connections, which is consistent with credential exfiltration patterns.
This rule detects when processes other than standard web browsers (Chrome, Edge, Firefox, Brave, Opera) attempt to read sensitive browser data files such as 'Login Data', 'Cookies', or 'Web Data'. These files contain stored credentials and session information, and unauthorized access is a common technique used by credential-stealing malware to exfiltrate sensitive user information.
This rule detects when a Node.js or NPM process accesses multiple sensitive browser credential files (Login Data or Cookies) within a short window, while simultaneously reading shell history files (bash_history, zsh_history, or fish_history). This behavior is characteristic of an automated credential harvester or infostealer script executing within a Node.js environment.
Detects Node.js processes accessing paths associated with cryptocurrency wallets and browser extension storage (MetaMask, Phantom, Exodus, Electrum). This behavior is characteristic of infostealer malware attempting to exfiltrate seed phrases, keys, or wallet configuration data.
This rule detects multiple unauthorized access attempts to files identified as machine learning models, weights, or checkpoints. It specifically looks for Security Event ID 4656 (Auditing of object access) where the object name contains keywords like 'model', 'weights', or 'checkpoint', and the access mask indicates unauthorized access attempts (0x0001 for ReadData or ListDirectory, 0x0002 for WriteData or AddFile). The rule then summarizes these attempts by user, computer, and hour, triggering an alert if 5 or more attempts are made within an hour.
This rule detects repeated access attempts (3 or more within an hour) to critical credential storage processes or files, specifically lsass.exe, the Security Account Manager (SAM) database, or the NTDS.dit file. Such activity is indicative of credential theft attempts by an adversary.
Page 44 of 76