Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
2,087 detections
Filters
Last updated
All Time
Detection languages
937
671
245
95
67
Contributors
798
791
99
59
31
Categories
1,168
1,065
225
210
171
Platforms
1,856
493
300
26
12
Products / Services
10,683
9,759
6,695
4,421
3,750
2,087
MITRE Techniques
760
704
336
308
240
CVEs
8
7
6
6
6
IDS Protocols
1
This rule detects the presence of unauthorized WebView or HTML overlay windows rendered on top of active banking applications on Android devices. This behavior is indicative of credential-theft malware, such as banking trojans, which use overlays to capture user input, including banking credentials, while masking their activity over legitimate finance-related applications.
Detects the execution of processes with suspicious file names that are commonly associated with masquerading, potentially impersonating legitimate software or system tools.
Detects when common torrent client applications spawn a child process that is an executable. This behavior is often associated with the execution of malicious payloads delivered or masqueraded as files within torrent environments.
Detects the execution of suspicious executables spawned from common torrent client applications. This rule monitors for known malicious file hashes or processes launched by torrent clients with suspicious naming patterns typically associated with pirated software or malware masquerading as media files (e.g., tags like 1080p, x264, bluray in executable names).
Detects the CastleRAT intermediate loader, which acts as a secondary stage before deploying SloppyRAT. The rule identifies the malicious payload by scanning for unique embedded strings, specific user-agent strings, and command-and-control (C2) communication patterns (domains and URI paths) within executable files.
This rule monitors network connections and DNS queries directed towards Microsoft's OAuth device code authorization endpoints ('/common/oauth2/deviceauth' or '/device'). This flow is frequently abused by adversaries to perform device code phishing, allowing them to gain access to a victim's account without requiring the user's password or bypassing traditional MFA.
Detects the execution of PowerShell commands intended to gather system information, specifically targeting the discovery of security software (anti-virus/EDR) and virtualization/sandbox artifacts. This behavior is indicative of an attacker performing environment reconnaissance to identify defensive controls or to determine if the payload is executing within an analysis environment.
Detects the use of common command-line utilities to search for sensitive files, including credential files (.env, credentials.json, database.yml), wallet files (wallet.dat), and mnemonic/seed phrases. This activity is often associated with reconnaissance for credentials or sensitive data on compromised Linux systems.
This rule detects the execution of Mimikatz or the use of its specific command-line arguments, which are strongly indicative of credential dumping activities, often used for post-exploitation lateral movement or privilege escalation.
This rule detects a multi-stage attack pattern originating from a web-based service. It identifies a web application process (like w3wp.exe, httpd.exe, or java.exe) spawning suspicious child processes (cmd.exe, powershell.exe, etc.), followed by the creation of new files and external network connections. This chain of behavior is highly indicative of web shell exploitation, post-exploitation command execution, and data exfiltration or C2 communication.
Detects processes associated with Acronis backup software executed by a user other than 'root', while the effective user context of the process is 'root'. This behavior often indicates an attempt to exploit setuid binaries or misconfigured permissions to execute commands with elevated privileges.
Detects the use of offensive security tools like Evil-WinRM or winrm-fs, which are often used by threat actors for remote administration, lateral movement, or backdoor delivery via the Windows Remote Management (WinRM) protocol.
This rule detects the use of 'npm' or 'node' to install packages from a registry other than trusted, standard registries (e.g., npmjs.org, GitHub). It specifically monitors command lines involving 'claude-code' that utilize custom, non-standard registry URLs. This behavior is indicative of potential supply chain attacks or the installation of unauthorized/malicious dependencies.
Detects the execution of cmd.exe with command-line arguments typical of self-deleting batch scripts. The pattern includes a delay (timeout /t 2) followed by a file deletion command (del), often used to remove temporary scripts or malicious artifacts after execution.
Detects the installation or update of browser extensions that utilize 'declarativeNetRequest' or 'webRequest' APIs in conjunction with 'content_scripts' and either broad URL access ('all_urls') or access to sensitive web domains (e.g., Google Gemini, Microsoft Copilot, Perplexity, Claude). This combination is highly indicative of extensions designed for data interception, credential theft, or unauthorized web traffic manipulation.
This rule detects potentially malicious file access patterns by the executable 'comet.exe'. It alerts when this process accesses sensitive files or directories associated with credentials, configuration files, or sensitive browser data, while explicitly excluding benign locations such as Chrome data folders and temporary directories.
Detects the execution of a hidden PowerShell process that subsequently spawns a child process using the 'Start-Process' cmdlet with the '-Verb RunAs' argument within a short time window. This pattern is commonly associated with attempts to bypass User Account Control (UAC) or execute processes with elevated privileges silently.
This rule detects anomalous, high-frequency actions performed by browser extensions that lack concurrent user interaction events (such as keyboard input, clicks, or gestures). It monitors for automated browser API calls or prompts originating from web browsers like Chrome, Edge, and Opera that exhibit potential malicious behavior, such as silent data collection, navigation, or unauthorized scripting.
Detects code injection attempts targeting the Windows Media Network Sharing Service (wmpnetwk.exe), specifically monitoring for the loading of suspicious or common networking-related DLLs into this process. This behavior is indicative of an adversary attempting to mask malicious activity within a legitimate system process.
Detects evidence of persistent Android malware attempting to maintain access. It identifies the execution of a hidden Go-based daemon masquerading as a shared library in temporary storage, silent reinstallation of malicious APKs using package installer flags, and automated re-granting of accessibility services to bypass user interaction requirements.
Detects suspicious Android application installation attempts using the 'pm install' command, triggered by processes or libraries named 'local-service' or 'liblocal-service.so'. This behavior is often associated with the manual side-loading of potentially malicious APK files in an Android environment.
Page 23 of 100