Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
4,421 detections
Filters
Last updated
All Time
Detection languages
4,217
105
40
25
13
Contributors
1,327
1,003
725
627
332
Categories
2,253
2,239
1,434
1,144
973
Platforms
4,107
453
295
83
82
Products / Services
10,670
9,759
6,693
4,421
3,749
MITRE Techniques
886
774
552
505
456
CVEs
18
12
12
12
10
IDS Classtypes
1,868
466
446
362
230
IDS Protocols
2,366
846
388
301
93
This rule detects attempts to abuse the macOS AuthorizationExecuteWithPrivileges function, which allows an application to execute a command with root privileges. The detection is based on the presence of the string "AuthorizationExecuteWithPrivileges" in HTTP response data, indicating a potential attempt by malware or an attacker to escalate privileges on a macOS system.
This rule detects potential PE injection payloads over HTTP by looking for the presence of both "NtUnmapViewOfSection" and "VirtualAllocEx" in the file data. These API calls are commonly used in process injection techniques, specifically for unmapping legitimate sections of a process and allocating new memory for malicious code.
This rule detects the delivery of a payload designed to bypass macOS Transparency, Consent, and Control (TCC) mechanisms via HTTP. Specifically, it looks for the string "kTCCServiceCamera" within HTTP response data, indicating an attempt to manipulate camera access permissions. This activity is often associated with privilege escalation techniques on macOS.
This rule detects network traffic containing the string "/etc/sudoers" over TCP port 22 (SSH). This could indicate an attempt to modify the sudoers file for privilege escalation, as the sudoers file controls which users can execute commands with superuser privileges.
This rule detects attempts to manipulate the sudo timestamp cache by looking for repeated 'sudo -n' commands within a short timeframe. The 'sudo -n' command allows sudo to run a command without prompting for a password, which can be abused by an attacker to maintain sudo privileges or bypass re-authentication if they have already compromised a user's session. The thresholding mechanism (10 times in 30 seconds from the same source IP) aims to reduce false positives from legitimate, infrequent uses of 'sudo -n' and focus on potential automated or rapid attempts to interact with sudo without password prompts, possibly to keep the timestamp alive or to quickly execute multiple commands.
This rule detects the delivery of a tool designed to bypass User Account Control (UAC) via HTTP. It specifically looks for HTTP responses containing the strings "IsUserAnAdmin" and "ShellExecute" (case-insensitive) within the file data, indicating the presence of code commonly used in UAC bypass techniques.
This rule detects potential Kerberos authentication abuse related to cross-domain trusts. It specifically looks for TCP traffic on port 88 (Kerberos) to the home network, containing the byte '6b' at the first position of the payload. A threshold of 20 occurrences within 10 seconds from the same source IP is set to trigger an alert, indicating a potential brute-force or rapid authentication attempt.
This rule detects attempts to modify a user's logon script via remote registry access. Specifically, it looks for TCP traffic on port 445 (SMB/CIFS, often used for remote registry) where the content "UserInitMprLogonScript" is present, indicating an attempt to alter this specific registry key. This activity is often associated with persistence techniques used by attackers to maintain access to a system.
This rule detects the creation of a new Azure AD user account via the Microsoft Graph API. It specifically looks for HTTP POST requests to 'graph.microsoft.com' with the URI containing '/users'. This activity could indicate an attacker establishing persistence by creating new accounts in a compromised Azure AD environment.
This rule detects attempts to update system firmware from an unverified source. It specifically looks for HTTP traffic (flow:to_client,established) where the URI contains the string "firmware" (case-insensitive) and the file data contains the byte sequence "AA 55". This combination suggests a potential firmware update being delivered over HTTP, which could be malicious if the source is not legitimate.
This rule detects a TFTP (Trivial File Transfer Protocol) boot file request. Specifically, it looks for UDP traffic destined for port 69 (the standard TFTP port) on the home network, containing the byte sequence "|00 01|" at a depth of 2 bytes. This pattern is characteristic of a TFTP read request (opcode 1). The rule's message suggests this could indicate a possible bootkit delivery attempt, as TFTP is often used in network booting scenarios.
This rule detects a port knocking sequence on closed ports. It triggers an alert when four TCP SYN packets are observed from the same source IP address within a 5-second window, targeting any port on the home network. This behavior is indicative of an attacker attempting to perform port knocking to open a hidden port or service.
This rule detects the download of Visual Studio Code (VS Code) or other Integrated Development Environment (IDE) extensions from official marketplaces (marketplace.visualstudio.com or open-vsx.org) when the downloaded file has a .vsix or .crx extension. This could indicate an attempt to install a malicious extension.
Botnet C2 Panel Access Detected
Suricata
This rule detects potential access to a botnet command and control (C2) panel. It triggers when HTTP URI requests contain both 'panel' and 'bot' (case-insensitive) within the URI. A threshold of 5 such requests from the same source within 60 seconds is set to reduce false positives.
This rule detects HTTP traffic where the referer header contains domains commonly associated with advertising networks (doubleclick.net, adnxs.com, googlesyndication) and the URI contains file extensions typically used for executable or script files (exe, ps1, msi, hta, vbs). This combination suggests a malvertising redirect attempt leading to the download of malicious files.
This rule detects HTTP traffic where the host header contains a domain with at least 8 alphanumeric characters followed by a common top-level domain (.com, .net, .org), and the URI contains the string 'gate' (case-insensitive). This pattern is indicative of a hijacked legitimate domain being used for Command and Control (C2) communication.
This rule detects the delivery of an Application Shim Database (.sdb file) over HTTP. Application Shims are used by Windows to ensure compatibility with older applications, but can also be abused by attackers for persistence and privilege escalation (e.g., by shimming malicious DLLs). Detecting the transfer of these files, especially over unencrypted HTTP, can indicate suspicious activity related to T1546.011 (Application Shimming).
This rule detects a brute-force attack against an SSH service on a network device management port. It triggers an alert if 15 or more TCP SYN packets are observed from a single source IP address to destination port 22 (SSH) within a 30-second window, indicating an attempt to establish multiple connections, characteristic of a brute-force attempt.
This rule detects attempts to register a Netsh helper DLL for persistence. Netsh (Network Shell) is a command-line scripting utility that allows you to display or modify the network configuration of a locally running computer. Attackers can abuse the 'add helper' command to register a malicious DLL, which will then be loaded by Netsh whenever it runs, providing a persistence mechanism. The rule specifically looks for TCP traffic on port 445 (SMB) containing the strings "netsh" and "add helper" in a case-insensitive manner, indicating an attempt to use this technique.
This rule detects the use of the 'trap' command with 'EXIT' in TCP traffic, which is a common technique used for persistence on Unix-like systems. Attackers can use the 'trap' command to execute arbitrary commands when a shell exits, ensuring their malicious code runs even after a session is closed.
This rule detects bulk email account creation attempts on free email providers ProtonMail and Tutanota. It triggers when a client makes 3 or more HTTP requests within 60 seconds to the signup page of either protonmail.com or tutanota.com.
Page 148 of 211