Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
18,128 detections
Filters
Last updated
All Time
Detection languages
6,549
6,208
1,473
1,005
661
Contributors
3,555
2,652
2,153
2,087
1,515
Categories
7,572
3,901
1,465
1,393
1,330
Platforms
13,733
1,392
1,319
824
738
Products / Services
3,828
3,137
2,448
912
908
MITRE Techniques
18,128
15,653
12,600
8,411
6,235
CVEs
19
18
17
16
14
IDS Classtypes
305
51
24
23
22
IDS Protocols
308
136
13
10
10
This rule detects attempts to access SNMP (Simple Network Management Protocol) services on the home network using the default community string 'public'. It specifically looks for the string 'public' within TCP traffic destined for port 161 (the standard SNMP port). A threshold of 5 attempts within 30 seconds from the same source IP will trigger an alert, indicating potential brute-force or reconnaissance activity against SNMP devices.
Flags suspicious execution of X-VPN.exe or related installers loading unexpected DLLs, consistent with the CWE‑427 uncontrolled search path exploited in the campaign.
This rule detects potential lateral movement attempts using alternate authentication material, specifically NTLMSSP, over SMB (port 445). It triggers an alert if five or more NTLMSSP authentications are observed from a single source IP address to the home network within a 30-second window. This behavior can indicate an attacker attempting to authenticate to multiple systems using stolen credentials or hashes.
This rule detects HTTP traffic where the URI contains both 'schtasks' and '/delay' (case-insensitive). This combination suggests an attempt to create a scheduled task with a delayed execution, which can be used by adversaries for sandbox evasion or persistence.
This rule detects the delivery of source code files (C, C++, C#, Java, Go, Rust) over HTTP to a client, specifically looking for content that includes 'main(' within the file data. This pattern suggests that a source code payload intended for compilation after delivery is being transferred, which could be indicative of malicious activity such as a staged attack where the attacker compiles and executes code on the victim's machine.
This rule detects potential sandbox evasion techniques by identifying HTTP responses containing a 'Sleep(' function call with a duration of 1,000,000 milliseconds (1000 seconds) or more. This long sleep duration is often used by malware to delay execution and bypass time-based sandboxes, which typically have limited execution times for analysis.
This rule detects the delivery of a raw volume access tool via HTTP. It specifically looks for HTTP traffic (flow:to_client,established) containing the strings "CreateFile", "\\.\", and "GENERIC_READ" within the file data. These strings are indicative of an application attempting to open a raw volume device for direct read access, often a technique used by malware or forensic tools to bypass file system controls.
This rule detects attempts to access physical drives directly over SMB by looking for the string "\\.\PhysicalDrive" in TCP traffic on port 445. This technique can be used by attackers to bypass file system access controls and directly read or write to disk sectors, often as part of defense evasion or data exfiltration.
This rule detects the potential reuse of an OAuth Bearer token from different IP addresses. It monitors HTTP traffic for the 'Authorization: Bearer' header and triggers an alert if the same token is observed from more than 20 distinct destination IP addresses within a 10-second window. This behavior can indicate an attempt to bypass authentication or session management, potentially through token theft or replay.
This rule detects HTML smuggling attempts by identifying the 'msSaveOrOpenBlob' API call within HTTP response bodies. This API is often used by attackers to deliver malicious files directly to a user's browser, bypassing traditional network security controls. The rule specifically looks for the case-insensitive string 'msSaveOrOpenBlob' in the file data of HTTP responses flowing from the server to the client.
This rule detects network traffic containing the strings "bcdedit" and "safeboot" over TCP port 445 (SMB). This combination suggests an attempt to remotely configure a system to boot into safe mode, which could be used by an attacker for defense evasion or to facilitate further malicious activities.
This rule detects the use of renamed system binaries (svchost, explorer, lsass, csrss) with appended digits (e.g., svchost1.exe) being used as proxy execution. It specifically looks for HTTP responses containing a Windows executable (MZ header) where the HTTP URI matches the pattern of these renamed binaries. This behavior is often indicative of defense evasion tactics by malware.
This rule detects attempts to purge mailbox data using Exchange Web Services (EWS) by looking for HTTP requests to '/EWS/Exchange.asmx' containing the 'HardDelete' string in the client body. This activity is indicative of an attacker attempting to remove evidence or sensitive information from a compromised mailbox.
This rule detects network traffic containing the string "/..namedfork/rsrc" (case-insensitive) over TCP to port 22 (SSH). This pattern is indicative of an attempt to use macOS resource forks to hide payload data, a technique often employed by malware for defense evasion. The detection specifically targets traffic originating from and destined for the home network, suggesting an internal system attempting to exfiltrate or receive hidden data.
This rule detects the creation of a new inbox rule via Exchange Web Services (EWS) that could be used to hide phishing replies. Specifically, it looks for HTTP traffic to '/EWS/Exchange.asmx' with 'NewInboxRule' in the client body, indicating an attempt to create a new inbox rule.
This rule detects attempts to unset the HISTFILE environment variable over a TCP connection to port 22 (SSH). Unsetting HISTFILE is a common technique used by attackers to prevent their commands from being recorded in the shell history, thereby evading detection and forensic analysis. The rule specifically looks for the string "unset HISTFILE" case-insensitively within the TCP stream.
This rule detects attempts to clear the Bash history using the 'history -c' command over an established SSH connection. It specifically looks for the case-insensitive string 'history -c' within TCP traffic flowing from the client to the server on port 22 (SSH). This activity is often associated with an attacker attempting to cover their tracks after gaining unauthorized access.
This rule detects HTTP traffic where the host header or URI contains keywords associated with virtual machine software (virtualbox, vmware, qemu) and the URI also contains the word "create". This combination suggests the potential creation or interaction with virtual machines, which could be used for defense evasion by adversaries to hide malicious activity.
This rule detects network traffic over SMB (port 445) that contains patterns indicative of a payload hidden within an NTFS Alternate Data Stream (ADS). Specifically, it looks for the string ":$DATA" followed by ".exe" (case-insensitive) in the TCP payload, which is a common technique used by malware to conceal executable files within legitimate files.
This rule detects network traffic containing the strings "SW_HIDE" and "CreateProcess" within file data in an HTTP response. This combination suggests an attempt to execute a process with a hidden window, which is a common technique used by malicious software to evade detection.
This rule detects attempts to modify an EC2 instance's attributes, specifically looking for the 'ModifyInstanceAttribute' API call to 'ec2.amazonaws.com'. This activity could indicate an attacker attempting to evade detection or alter the instance's configuration for malicious purposes.
Page 453 of 864