Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
340 detections
Filters
Last updated
All Time
Detection languages
121
95
28
25
18
Contributors
111
38
29
22
22
Categories
228
127
108
46
28
Platforms
255
58
57
11
10
Products / Services
77
70
29
21
17
MITRE Techniques
18,115
15,635
12,576
8,388
6,215
CVEs
2
2
1
1
1
IDS Classtypes
7
1
IDS Protocols
8
Detects anomalous credential access behavior in Azure Key Vault where a single identity performs more than 20 secret, key, or certificate read/list operations within a 5-minute window. This behavior is indicative of potential unauthorized reconnaissance or exfiltration of secrets stored in Key Vaults, excluding known automation service principals.
Campaign converting compromised FortiGate firewalls into credential stealers
This rule detects shell commands (bash, sh, zsh) initiated by AI-agent or development-related processes (e.g., Python, Claude Desktop, openclaw) that target sensitive macOS paths associated with credentials, SSH keys, crypto wallets, and browser cookies, a technique characteristic of the Atomic Stealer (AMOS) malware.
Detects potential data exfiltration by monitoring interpreter processes (Python, Node.js) that access sensitive local credential/configuration files and subsequently connect to known cloud storage or code repository APIs (Dropbox, GitHub, Google Cloud). The rule correlates file access events with network connection activity.
Detects bulk file access or modifications in sensitive directories (Desktop, Documents, Downloads) targeting credential and document files (ovpn, kdbx, jks, eml, docx, xlsx, pdf), or direct PowerShell access to OpenVPN configuration or KeePass database files. This behavior is indicative of data staging or exfiltration activities associated with the GIFTEDCROOK stealer.
This rule detects shell commands (bash, sh, zsh) initiated by AI-agent or development-related processes (e.g., Python, Claude Desktop, openclaw) that target sensitive macOS paths associated with credentials, SSH keys, crypto wallets, and browser cookies, a technique characteristic of the Atomic Stealer (AMOS) malware.
Detects anomalous or unauthorized processes accessing sensitive AI configuration files, SSH configurations, version control files, and shell history within a short time window. The rule flags instances where non-standard or unexpected applications exhibit broad or high-frequency access to these files, which are common targets for credential harvesting or exfiltration by adversaries.
This rule detects suspicious activities originating from Python processes spawned by development tools like VS Code, Node.js, or npm. It flags potential credential access when such processes attempt to read sensitive files (e.g., browser profiles, SSH keys, cloud configuration files) or perform suspicious network communication to external, non-standard ports, which may indicate data exfiltration or command-and-control behavior.
Detects the node.exe process (npm lifecycle) accessing sensitive web browser credential databases (e.g., Login Data, Cookies, Web Data, and Firefox profiles). This activity is indicative of infostealer malware, such as Miasma or MYRA, which often leverages malicious npm packages to drop and execute SQLite-based credential exfiltration logic directly from disk.
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.
Campaign converting compromised FortiGate firewalls into credential stealers
Fraud framework powering scam domains for crypto and gambling schemes
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.
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.
This rule detects potential unauthorized access to web browser data files (such as Login Data, Cookies, or History) by processes other than the legitimate browser applications. It also identifies process command-line arguments often used by malicious tools to access browser data or bypass protections, which is a common indicator of credential theft from browsers.
This rule detects the invocation of local AI/LLM CLI utilities (e.g., ollama, llama-cpp) by potentially malicious or automated parent processes. It specifically flags scenarios where non-interactive or scripting-based processes (such as WScript, PowerShell, or Python) attempt to use these AI tools, particularly when the command line includes keywords related to sensitive data discovery, such as 'password', 'token', or 'private key'. This behavior is characteristic of infostealer activity (e.g., QUIETVAULT) attempting to use AI tools for automated reconnaissance and credential extraction.
Detects node.exe (often associated with malicious npm package runtimes) accessing local credential store files such as KeePass, 1Password, and Bitwarden. This activity is indicative of infostealer payloads (e.g., Miasma/MYRA) targeting developer workstations to exfiltrate sensitive credential databases.
Detects node.exe or npm processes accessing directory paths associated with popular browser cryptocurrency wallet extensions, a behavior indicative of the Miasma infostealer used in supply chain attacks.
Detects Node.js or npm processes accessing sensitive developer configuration and credential files. This rule is designed to identify malicious supply chain activity, specifically matching patterns where npm postinstall scripts or malicious node modules attempt to exfiltrate files such as .gitconfig, SSH keys, cloud credentials, and tokens from a developer workstation.
Detects suspicious process activity originating from common build and package management tools (node, npm, bun, npx) that targets sensitive cloud and container credential locations, such as AWS IMDS, AWS configuration files, Kubernetes service account tokens, and HashiCorp Vault secrets. This rule is designed to identify malicious post-installation scripts or build processes attempting to exfiltrate credentials from developer or CI/CD environments.
This rule detects scenarios where development tools such as VS Code (Code.exe) or npm spawn multiple child processes of Python or Node.js interpreters within a short time window, followed by those same interpreters accessing sensitive credential files (e.g., SSH keys, browser login data, or cloud configuration files). This pattern is indicative of a developer workstation compromise or a supply chain attack involving malicious code execution.
Page 8 of 17