Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
7,144 detections
Filters
Last updated
All Time
Detection languages
3,228
1,086
498
478
469
Contributors
1,824
1,607
872
505
300
Categories
2,979
2,473
1,063
1,026
910
Platforms
39,802
7,144
6,519
3,861
3,601
Products / Services
1,325
1,070
970
655
490
MITRE Techniques
2,231
1,319
1,319
876
873
CVEs
66
65
33
32
28
IDS Classtypes
81
80
56
27
10
IDS Protocols
149
98
6
5
4
Detects the use of iptables to drop incoming SSH traffic (port 22) on Linux, a behavior observed in KadNap botnet infections. This rule specifically looks for the execution of the `iptables` command with parameters to set an INPUT rule, specify TCP protocol, target destination port 22, and set the jump target to DROP.
Detects administrative actions to disable or unload the 'algif_aead' kernel module. Monitoring for this activity helps defenders verify successful automated deployment (e.g., via Ansible) of the recommended security fix for CVE-2026-31431 (CopyFail).
This rule detects outbound network connections from endpoints to specific, potentially suspicious, IPv4 address ranges (162.220.234.0/24 and 162.220.232.0/24). Such connections could indicate command and control (C2) activity, data exfiltration, or communication with malicious infrastructure.
Detects a Python process attempting to access the memory of another process via the /proc filesystem. This behavior was observed in the Shai-Hulud SAP CAP supply chain attack, where a Python script dumped the Runner.Worker process memory to extract short-lived, high-value tokens passed between CI workflow steps.
Detects modifications to the OpenClaw agent's SOUL.md file, which dictates the core behavior and instructions of the agent. Attackers exploit this by tampering with the file to persistently alter the agent's actions across all future sessions without needing traditional code execution, as seen in attacks against NVIDIA NemoClaw sandboxes.
Susp AWK Command Execution
Gravwell
This rule detects suspicious execution of the 'awk' command on Linux systems. Specifically, it looks for 'awk' commands that include suspicious patterns. This pattern is often indicative of malicious script execution or code injection attempts using 'awk' for arbitrary command execution.
Detects pip or pip3 installation commands targeting the specific compromised version of the elementary-data PyPI package. Installation of v0.23.3 indicates exposure to the supply chain compromise regardless of whether the marker file was subsequently observed. Also catches generic 'pip install elementary-data' without a version pin, which during the active window (2026-04-24 22:20 UTC to 2026-04-25 ~11:51 UTC) would have pulled the malicious version.
This rule detects the execution of specific Linux utilities that can be used to gather system information, related to virtualization and hardware details. Adversaries often use these tools during the discovery phase to understand the environment they have compromised and adjust accordingly.
Detects the execution of 'awk' with command-line arguments that indicate it's being used to execute system commands or scripts. This often signifies malicious activity where 'awk' is leveraged for arbitrary command execution.
This rule detects attempts to modify GRUB configuration files using common text editors. Adversaries may modify GRUB configuration to establish persistence, disable security features, or alter the boot process for malicious purposes.
This rule detects the presence of suspicious script content (e.g., 'system(', 'exec(', '/dev/tcp/') within Python (.py) or shell (.sh) files located in common plugin directories on Linux systems. This could indicate an attempt to inject malicious code into package management configurations for persistence or privilege escalation.
This rule detects the execution of common system enumeration commands (lsblk, hostname, mount, uname) within a Docker container, when the container is run with privileged access. This activity could indicate an adversary attempting to glean information about the container environment.
Detects the execution of 'awk' with command-line arguments that indicate it's being used to execute system commands or scripts. This often signifies malicious activity where 'awk' is leveraged for arbitrary command execution.
Detects the execution of the 'dvr' downloader script and subsequent 'nexuscorp' payload executions used by the Nexcorium Mirai variant botnet. This rule specifically looks for `wget` downloading 'dvr' from an IP address, direct execution of './dvr', or execution of 'nexuscorp' with an architecture-specific 'dvr' payload.
Detects the creation of 'vector_notice.sh' in '/etc/profile.d/', a shell script dropped by VECT ransomware on Linux systems to display its ransom note upon user login. This rule specifically looks for file creation events on Linux systems where the target file name matches the exact path '/etc/profile.d/vector_notice.sh'.
Detects execution of shell commands interacting with busybox (e.g., 'cat /bin/busybox'). This behavior is used by the Nexcorium Mirai variant to verify shell functionality after a successful Telnet brute-force attack.
This rule detects the execution of SUID binaries by a non-root user, immediately followed by the creation of a persistence mechanism such as a systemd service file or a cron job. This correlation aims to identify potential privilege escalation attempts where an attacker uses an SUID binary to gain elevated privileges and then establishes persistence on the system.
Detects DNS requests to file.io originating from non-browser processes, indicative of data exfiltration, potentially by tools like CompactGopher. The rule identifies DNS requests for file.io or its subdomains, joins them with process information, and then filters out common web browsers to highlight suspicious activity.
Detects the creation of an executable file named 'sysd' in the '/usr/local/bin/' directory on Linux systems. The Nexcorium Mirai variant copies itself to this location to masquerade as a legitimate system process for persistence. This specific file name is not a standard Linux system daemon.
This rule detects the use of 'openssl' or 'base64' for decoding data piped into a shell (bash, sh, zsh) or scripting interpreter (python, perl). This pattern is often used by adversaries to decode obfuscated commands or payloads directly into memory for execution, bypassing disk-based detection.
Detects the use of esxcfg-advcfg to alter the BufferCache settings (MaxCapacity or FlushInterval) on an ESXi host. This activity is often associated with ransomware variants like Gentlemen ransomware, which modify these settings to prepare the storage layer for fast, reliable bulk file encryption.
Page 277 of 341