Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
7,142 detections
Filters
Last updated
All Time
Detection languages
3,220
1,086
504
478
469
Contributors
1,824
1,607
872
505
300
Categories
2,971
2,472
1,061
1,026
908
Platforms
39,776
7,142
6,518
3,852
3,601
Products / Services
1,324
1,069
971
657
488
MITRE Techniques
2,230
1,317
1,314
873
871
CVEs
66
65
33
32
28
IDS Classtypes
81
80
56
27
10
IDS Protocols
149
98
6
5
4
Detects suspicious file creation or execution of Node.js scripts linked to VS Code or .claude directories. This behavior often suggests the presence of poisoned IDE configurations or malicious task automation attempts designed to execute code when a project or IDE folder is opened.
Detects multiple techniques associated with Linux post-exploitation and persistence, including LD_PRELOAD environment variable hijacking, suspicious cron jobs, profile.d persistence modifications, systemd service masquerading via prctl, and fileless execution via memfd_create.
Detects process start events where the command line contains the specific string 'ShitSetupOn26126k'. This appears to be a specific indicator of compromise (IOC) related to a custom script or malware installation routine.
Detects the use of Amazon Q related configuration files (.amazonq, mcp.json) in conjunction with common command-line utilities such as bash, sh, npx, or node. This activity may indicate an attempt to interact with or exploit developer tools and environment configurations to perform unauthorized reconnaissance or execution.
Detects instances where common IDE-related processes (like VS Code, Amazon Q, or Node) spawn a shell to execute AWS CLI commands specifically focused on identifying the current caller identity using 'aws sts get-caller-identity' and 'curl'. This pattern often indicates attempts to verify compromised AWS credentials or discover account details from an environment.
Detects the execution of common command interpreters (node, python, shell) or processes with 'mcp' in the command line that reference sensitive cloud-related environment variables or identity-related commands, such as AWS access keys, session tokens, or SSH authentication sockets. This indicates potential credential theft or unauthorized cloud resource access.
Detects execution patterns indicative of exploitation attempts against the CVE-2024-1086 Linux kernel vulnerability. The rule identifies suspicious usage of networking tools ('tc' with 'pedit'), namespace manipulation ('unshare'), AppArmor profile bypasses ('aa-exec'), and specific malicious binary names associated with proof-of-concept exploits for this vulnerability.
Detects the use of the 'unshare' utility to create new namespaces on Linux systems. Adversaries often use 'unshare' to perform container escapes, escalate privileges, or isolate processes from host-level monitoring. This rule specifically filters out legitimate administrative or container management processes such as systemd, containerd, and runc to reduce noise.
Detects instances where the Amazon Q Developer extension spawns suspicious child processes, such as bash or npx, which may indicate the execution of arbitrary commands defined in a potentially malicious .amazonq/mcp.json workspace configuration file.
Detects process execution or file creation/modification events associated with the PACKET_EDIT_MEME (pedit_cow_demo) exploit, which targets Linux kernel vulnerabilities (CVE-2026-46331) for local privilege escalation.
Detects instances where the /bin/su binary is executed by a non-root process but succeeds in launching as the root user. This behavior is indicative of potential memory-based privilege escalation exploits, such as page cache poisoning (e.g., pedit COW variants), which allow unauthorized SUID binary execution without modifying the binary on disk.
This rule detects unprivileged processes executing Linux traffic control (tc) commands that leverage the 'act_pedit' action. Such behavior is highly unusual for non-root users and matches the exploitation pattern of the CVE-2026-46331 pedit copy-on-write (COW) kernel vulnerability, which attempts to escalate privileges via netlink socket operations.
Detects modification of /etc/ld.so.preload to register the MYRA RAT rootkit shared library (.libcache.so) for system-wide LD_PRELOAD injection. The MYRA npm package (apintergrationpost) copies libcache.so to /usr/local/lib/.libcache.so and appends its path to /etc/ld.so.preload, causing the rootkit to load into every new process on the system.
Detects web server processes (e.g., httpd, nginx) spawning common shell interpreters (sh, bash, cmd.exe) that execute suspicious commands often used in reconnaissance or download stages of an attack, such as 'whoami', 'wget', or 'curl'. This behavior is characteristic of an exploited web application being used as a staging or command-and-control pivot point.
Detects the node.exe process attempting to read shell history files (.bash_history, .zsh_history, etc.), which are common targets for credential harvesting by malicious npm packages. This behavior is associated with the Polymarket Trap campaign involving Miasma and MYRA infostealers.
Detects node.exe processes attempting to access sensitive browser credential databases, such as cookies, login data, or key databases. This pattern is indicative of infostealer malware, specifically those associated with the Polymarket Trap supply-chain campaign, which abuse node.js processes to exfiltrate browser data.
Detects suspicious modifications to file permissions and attributes on specific artifacts (lambsys, procq, isp.sh) known to be associated with the Lambsys cryptominer campaign. The rule monitors for execution of chmod or chattr on these artifacts, or any generic chmod activity within /tmp or /var/tmp directories.
Detects the execution of 'unshare' by an unprivileged user to create a new user namespace, followed by a write operation to '/proc/self/uid_map', '/proc/self/gid_map', or '/proc/self/setgroups'. This sequence is a known technique for local privilege escalation (LPE) vulnerabilities, such as those related to unprivileged user namespaces.
Detects node.js executing known malicious npm lifecycle scripts (such as install-check.cjs, verify-peer.cjs, sync-peer.cjs, postinstall-run.js, and preinstall.js) often found in node_modules folders. These scripts are associated with the Polymarket Trap supply chain campaign, which leverages malicious npm hooks for initial access or malicious activity within a development environment.
Detects the execution of Node.js or npm processes that reference known malicious transitive npm dependencies or typosquatted packages identified in the Polymarket Trap supply chain campaign, such as 'log-taker' and various 'thirdweb' typosquats.
Detects a single process reading both SSH private keys and various developer-sensitive configuration or credential files (e.g., .aws/credentials, .npmrc, .pypirc) on a single host. This behavior is consistent with infostealer activity, such as the Miasma JavaScript infostealer used in supply chain campaigns, aiming to harvest credentials from developer workstations.
Page 226 of 341