Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
20,499 detections
Filters
Last updated
All Time
Detection languages
8,114
7,174
1,351
1,169
1,063
Contributors
4,878
2,724
2,695
2,646
2,356
Categories
20,499
11,881
5,887
5,179
4,868
Platforms
18,094
3,056
1,506
124
104
Products / Services
5,726
4,303
3,716
1,175
958
MITRE Techniques
9,492
7,575
3,460
2,848
2,703
CVEs
36
28
25
21
20
IDS Classtypes
1
Detects outbound network connections to common Mythic C2 ports initiated by processes identified as compiler-related binaries (Go, Zig, Rust) or binaries running from suspicious, user-writable directories (Temp, AppData, etc.). This behavior is consistent with the execution of staging or initial implants associated with the Mythic post-exploitation framework.
Detects a potential exploitation of CVE-2026-12957, where a malicious git repository contains an MCP (Model Context Protocol) configuration file. When this workspace is opened, the Amazon Q Developer extension for VS Code improperly processes this configuration, resulting in the unauthorized execution of shell processes (cmd.exe, powershell.exe, bash, or sh) by the extension's host processes (code.exe or node.exe).
Detects attempts to suppress PowerShell ETW telemetry by modifying the PSEtwLog object (setting it to null or 0) in conjunction with indications that AMSI initialization has failed, suggesting a coordinated effort to blind security monitoring during malicious script execution.
Detects artifacts, execution of harness tooling, and post-exploitation behavior associated with CVE-2026-55200 in libssh2. The rule monitors for the presence of known exploit filenames (libpwn), suspicious Python script execution, unexpected shell spawning from SSH-enabled clients, and outbound network connections to non-standard ports typical of exploit scaffolding.
Detects instances where AI coding agents, specifically Claude or Node-based environments, initiate secondary processes like git clone, package installation (pip, npm), or script execution. This behavior often suggests the agent is autonomously pulling and executing code from external repositories without explicit human approval, posing a significant risk of supply chain compromise.
Detects the drop or installation of known vulnerable drivers associated with the 'The Gentlemen' ransomware group's Bring Your Own Vulnerable Driver (BYOVD) tactics, or the creation of kernel-mode services by unsigned binaries. These techniques are often used to gain kernel-level privileges and disable security software.
This rule detects attempts to bypass the Antimalware Scan Interface (AMSI) by monitoring processes such as PowerShell, cscript, wscript, and mshta for command-line arguments that attempt to modify AMSI memory structures. It specifically looks for patterns involving AmsiInitialize, memory nullification, and the loading of amsi.dll using techniques like DllImport or Add-Type.
Detects instances where a non-root user executes the 'sudo' command in combination with 'tee'. This pattern is frequently used to bypass file permission restrictions by appending or writing content to sensitive system files that would normally require root privileges, a common method for privilege escalation or maintaining persistence.
This rule detects the modification or creation of sensitive Linux files often used for persistence, such as cron job configurations, system boot scripts, and custom system tools. It monitors for file writing and process execution events involving specific paths and filenames identified as associated with persistence mechanisms or monitoring tools.
This rule detects potential persistence via Windows Registry Run keys by monitoring for the creation or modification of values pointing to suspicious paths (e.g., AppData, Temp, winupdate.exe). It also identifies suspicious execution of files originating from user-writable directories, specifically looking for indicators of PyInstaller-packaged executables or specific known malicious hashes, which are frequently used by adversaries for malware deployment.
Detects the use of the Windows 'netsh.exe' utility to perform network port proxying or tracing configurations, initiated by common command-line shells (cmd.exe, powershell.exe). Attackers may use these capabilities for lateral movement, persistence, or to sniff network traffic.
Detects the execution of known malicious or hijacked npm and Go packages associated with the Lazarus Group 'Contagious Interview' supply chain campaign. The rule monitors for node.exe or go.exe spawning unexpected child processes like shells or download utilities (e.g., curl, powershell) and the presence of specific malicious package names in command lines.
Detects Python processes spawned by development tools (VSCode, Cursor) or Node.js that are engaged in suspicious activities, specifically communicating with the Telegram Bot API or uploading large amounts of data, often accompanied by file staging (ZIP archive creation). This behavior is characteristic of the InvisibleFerret information stealer.
Detects malicious activity associated with the Yuta/Glove Stealer malware family. The rule identifies attempts to register persistent WMI event subscriptions (using wmic, powershell, or pwsh) to trigger execution or the registration of low-level keyboard hooks (WH_KEYBOARD_LL) for keylogging, originating from suspicious process paths like winupdate.exe or PyInstaller-compiled temporary directories.
Detects file and directory hiding techniques associated with Mustang Panda implants (e.g., SHARDLOADER, ZOHOMURK) by monitoring for the usage of 'attrib.exe' to set the hidden (+h) attribute, or the usage of 'icacls.exe' to manipulate access permissions within sensitive directories like ProgramData or AppData, which may be indicative of malicious artifact concealment.
Detects malicious attempts to clear Windows Event Logs using native utilities like wevtutil or PowerShell, or by direct file deletion of .evtx files. This behavior is common in post-exploitation cleanup phases by threat actors, such as The Gentlemen RaaS, to hinder incident response and forensic analysis.
Detects Microsoft Office applications spawning common LOLBAS (Living Off the Land Binaries and Scripts) such as PowerShell, CMD, WScript, or MSHTA. This activity is a common indicator of macro-based attacks or document-based exploitation attempting to execute arbitrary code or scripts.
This rule monitors for the execution of common remote access and support tools (AnyDesk, TeamViewer, ScreenConnect, QuickAssist) that originate from suspicious file paths (e.g., Temp, AppData, Downloads) or are launched with silent installation flags, or appear to be installed via msiexec by non-standard parent processes. These behaviors are common indicators of adversaries attempting to establish unauthorized persistent remote access or deploying remote support tools as part of a post-exploitation activity.
Detects the execution or loading of executables (.exe) or dynamic link libraries (.dll) located in user-specific temporary or roaming directories (AppData). These directories are common locations for attackers to drop payloads, execute malicious code, or achieve persistence, as they are writable by standard users without elevated privileges. The rule includes filters for known legitimate processes that may perform operations in these directories to reduce noise.
This rule detects multiple behavioral indicators associated with malware deployment, including PyInstaller environment artifacts, reconnaissance via system utilities (wmic, tasklist), and suspicious process hollowing/stager chains (e.g., mshta/wscript/cscript invoking PowerShell followed by payload execution from temporary directories). These behaviors are often associated with loaders like BQTLock and Remcos.
This rule detects multi-stage behavior associated with the BQTLock ransomware, including C2 network communication, execution of loaders (PyInstaller-based) from common writable directories, suspicious child process spawning, unauthorized OpenSSH service usage potentially indicating privilege escalation, and mass file encryption indicated by both specific file extensions and bulk rename heuristics.
Page 364 of 977