Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
2,918 detections
Filters
Last updated
All Time
Detection languages
1,568
780
216
110
94
Contributors
703
507
419
236
211
Categories
20,456
11,839
5,876
5,155
4,865
2,918
Platforms
2,584
507
385
83
17
Products / Services
1,265
605
83
82
72
MITRE Techniques
841
797
582
344
307
CVEs
24
8
8
5
5
Detects unauthorized processes attempting to read, modify, or create files within common browser credential locations (Chrome, Firefox, Edge, and Windows Credential Manager). Legitimate browser processes and their known signers are excluded, focusing on suspicious secondary processes or tools frequently utilized by infostealers like Lumma and RedLine to dump credentials.
Detects unauthorized access or modification to common CI/CD credential files (.npmrc, .pypirc, .git-credentials, jenkins credentials.xml) and CI/CD configuration files (.github/workflows, .gitlab-ci.yml). The rule monitors both file system activities by non-standard processes and the execution of command-line tools that reference these sensitive files.
Detects instances where non-browser processes access sensitive browser-related files (Login Data, Cookies, or Local State) located within AppData directories. This behavior is highly indicative of credential and session token theft, often associated with AiTM or post-compromise information harvesting activities.
Detects unauthorized or non-standard processes attempting to create, modify, or access sensitive cloud configuration and credential files, such as AWS credentials, Azure CLI token caches, or GCP application default credentials. This behavior is indicative of potential credential theft or unauthorized access to cloud environment tokens.
Detects unauthorized access or modification to common CI/CD credential files (.npmrc, .pypirc, .git-credentials, jenkins credentials.xml) and CI/CD configuration files (.github/workflows, .gitlab-ci.yml). The rule monitors both file system activities by non-standard processes and the execution of command-line tools that reference these sensitive files.
This rule detects unauthorized processes attempting to create, modify, rename, or delete the 'Login Data' SQLite database files used by Google Chrome and Microsoft Edge to store saved credentials. By excluding legitimate browser processes and updates, the rule identifies potential credential theft attempts by infostealer malware or unauthorized actor tools.
This rule detects any activity within Office 365 logs that includes a 'username' field and then projects a SHA256 hash of a 'file.exe'. While the specific detection logic is incomplete, it indicates an attempt to correlate Office 365 user activity with file execution or manipulation, potentially for forensic analysis or to identify suspicious file interactions.
This rule detects the creation or modification of executable files (.com, .exe, .scr, .pif, .bat, .cmd) in common user directories (Documents, Downloads, Desktop) where the initiating process is a legitimate application like explorer.exe, winrar.exe, or 7z.exe. This pattern is often used in phishing attacks where malicious executables are disguised as benign documents.
Detects the installation of known malicious PyPI packages ('frint', 'skytext', 'slogsec', 'logcrypt.cryptography') associated with the ChocoPoC supply chain campaign. The rule monitors process execution commands related to 'pip' package installation and tracks the appearance of malicious compiled extension files ('gradient.pyd', 'gradient.so') on the filesystem.
Detects file creation, copy, or rename operations within known VPN application directories (CyberGhost, ExpressVPN, NordVPN) when initiated by Chromium Embedded Framework (CEF) related processes (CefSharp.BrowsersSubprocess). This behavior is highly irregular as standard web browser components should not be modifying the local configuration or installation directories of VPN software.
Detects malicious Python or JavaScript package archives (such as those used in dependency confusion attacks) that contain obfuscated code execution logic (base64 encoded commands) within package installation hooks (setup.py), or those embedding suspicious binary executables (PE/ELF headers) within the package structure.
Detects the file-based installation of known malicious Chrome extensions (specifically Adblock for YouTube, Adblock for Chrome, Adblock for You, and AdBlock Suite) that contain mechanisms for executing remote malicious scripts.
Detects the presence of known malicious variants of the 'Adblock for YouTube' Chrome browser extension within the user's Chrome extensions directory. These extensions are flagged for utilizing broad host permissions to maintain persistent silent access and potential remote code execution via fetched scriptlets.
Detects STOCKSTAY .NET backdoor components (e.g., STOCKMARKET, STOCKTRADER) accessing their encrypted 'fonts' configuration files located in the local application data SMN directory. These components use environmental keying (hostname or domain-based) to decrypt the configuration, a technique designed to thwart analysis.
Detects GreenBlood ransomware activity targeting network shares and USB drives. This rule identifies file rename or creation events with specific ransomware extensions (.tgbg, .bak) or ransom note filenames ('READ_ME_TO_RECOVER_FILES.txt'), combined with the use of extended path prefixes (\?\ or \?\UNC\) often employed by ransomware for network/UNC path targeting. The rule aggregates these events and alerts if three or more such files are detected from a single process on a device.
Detects the execution of a process named 'servertool.exe' specifically when it originates from a user's OneDrive Music folder or a generic Music folder within the user profile. This could indicate an attempt to masquerade malicious activity by placing an executable in an unusual, typically benign location.
Detects the execution of suspected StrikeShark-related binaries (SystemSettings.exe and FScan) when they are found running from non-standard directories or masquerading as legitimate system processes. The rule specifically monitors for instances where these binaries are executed from user-writable paths like AppData or Temp, while excluding legitimate Windows paths and processes associated with Windows Update.
This rule detects potential memory-resident malware or staging activity by identifying instances where a high volume of DLL, OCX, or SYS files are loaded from user-writable directories (Temp, AppData, Users) on a specific device within a one-hour window. A threshold of 5 or more unique image loads from these locations is flagged as potentially suspicious, as it may indicate an attacker loading multiple malicious components or modules.
This rule detects files matching known SHA256 hashes associated with the VoidLink malware framework. This is a high-fidelity indicator with a very low chance of false positives.
This rule detects potential memory-resident malware or staging activity by identifying instances where a high volume of DLL, OCX, or SYS files are loaded from user-writable directories (Temp, AppData, Users) on a specific device within a one-hour window. A threshold of 5 or more unique image loads from these locations is flagged as potentially suspicious, as it may indicate an attacker loading multiple malicious components or modules.
Detects instances where common shell or command-line tools are spawned by Amazon Q processes (amazonq-language-server) or development-related processes (Code.exe, node) shortly after the creation or access of the 'mcp.json' configuration file within an '.amazonq' directory. This behavior may indicate an attacker using development tool vulnerabilities or compromised extensions to execute arbitrary commands.
Page 84 of 139