Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
4,866 detections
Filters
Last updated
All Time
Detection languages
1,757
1,593
604
243
199
Contributors
944
801
787
614
315
Categories
20,463
11,850
5,879
5,158
4,866
Platforms
3,711
737
612
405
100
Products / Services
1,458
648
498
272
235
MITRE Techniques
1,330
1,214
888
785
772
CVEs
7
5
5
5
5
IDS Classtypes
546
20
16
5
4
IDS Protocols
417
66
60
39
13
This rule detects the presence of the string 'document.write(unescape(' in HTTP response bodies. This pattern is commonly used in web-based attacks to inject malicious content, often obfuscated, into legitimate web pages served to clients. The 'flow:to_client,established' indicates that the rule is looking at traffic flowing from the server to the client over an established connection, specifically within the HTTP data payload ('file.data'). The 'nocase' option ensures the detection is case-insensitive.
This rule detects attempts to download malware builder tools (such as builders, generators, crypters, or packers) from raw.githubusercontent.com. It specifically looks for HTTP traffic where the host is 'raw.githubusercontent.com' and the URI contains keywords commonly associated with malware development tools.
This rule detects HTTP responses that originate from search engines (Google, Bing, Yahoo) and contain a Windows executable (MZ header) in the file data. This behavior is indicative of SEO poisoning, where malicious actors manipulate search engine results to redirect users to malware downloads.
Detects the specific ClickFix execution chain used to download, extract, and execute the MLTBackdoor payload via cmd, curl, tar, and rundll32. This rule identifies the execution of 'cmd.exe' with a command line containing a sequence of 'curl' for downloading, 'tar' for extraction, and 'rundll32' for execution, which is characteristic of the MLTBackdoor's delivery and execution mechanism.
Detects the specific ClickFix execution chain used to download, extract, and execute the MLTBackdoor payload via cmd, curl, tar, and rundll32. This rule identifies the execution of 'cmd.exe' with a command line containing a sequence of 'curl' for downloading, 'tar' for extraction, and 'rundll32' for execution, which is characteristic of the MLTBackdoor's delivery and execution mechanism.
This rule detects the delivery of a JavaScript payload that has been hex encoded. It specifically looks for the hex representation of the string "script" (\x73\x63\x72\x69\x70\x74) within HTTP response data flowing to the client. This technique is often used by attackers to obfuscate malicious JavaScript code and evade signature-based detection.
This rule detects DNS TXT record responses containing a Base64 encoded payload of at least 60 characters. This pattern is often used by malware for command and control (C2) communication or data exfiltration, leveraging DNS tunneling to evade detection.
Detects the Miasma/Hades langchain-core-mcp malicious Python startup-hook loader
Detects the creation of temporary '.tmp' files starting with 'Hid' in the user's temporary directory, which is indicative of the PoisonX dropper deploying its driver. This behavior is associated with the initial stages of PoisonX malware execution.
This rule detects an unusually high volume of file deletion events on a device within a short time frame (100 or more files deleted within a 5-minute window). This activity can be indicative of malicious behaviors such as ransomware encrypting and deleting original files, data wiping attacks, or an adversary attempting to remove forensic evidence by deleting logs or other critical files.
This rule detects an unusually high number of file rename events (20 or more within a 1-hour window) initiated by a single process account. This behavior can be indicative of malicious activities such as data staging prior to exfiltration, ransomware encryption, or attempts to evade detection by renaming malicious files or legitimate system utilities.
Detects the creation of an MSI (Microsoft Installer) file on a device where the file's origin referrer URL indicates it was downloaded from a ZIP archive that was originally an email attachment. This could indicate a user opening a malicious ZIP file from an email, leading to the execution of an installer.
This rule detects when a file, initially received as an email attachment, is subsequently observed on multiple endpoints within a 7-day period. It correlates SHA256 hashes from email attachment logs with device file events to identify widespread propagation of potentially malicious attachments.
This rule detects the creation or modification of registry run keys that contain specific keywords associated with PlugX malware and the Mustang Panda threat group. It specifically looks for modifications to the 'Run' key under 'Software\Microsoft\Windows\CurrentVersion' in the registry, which is a common persistence mechanism. The keywords 'plugx', 'mustang', 'panda', and 'plug' are used to identify suspicious registry value data.
Detects connections to domains associated with observed ACR Stealer command-and-control infrastructure.
Detects multiple registry value set events where the registry value data contains keywords like 'ransom' or 'payment', or the registry key contains 'Run'. This behavior can indicate ransomware activity attempting to establish persistence or communicate its demands.
This rule detects a single process creating a large number of files with diverse file types within a short time frame (5 minutes). This behavior can be indicative of malicious activity such as ransomware encrypting files, data staging for exfiltration, or malware dropping multiple components.
This rule detects attempts by a device to resolve specific domain names known to be associated with ransomware killswitches. Successful resolution of these domains could indicate a ransomware infection attempting to halt its encryption process.
This rule detects the staging (creation, modification, or renaming) and subsequent execution of executable files (.exe) within the 'C:\Users\Public\Music\' directory. This folder is an unusual location for executables and is often leveraged by adversaries for staging malicious payloads to evade detection. The rule specifically references 'Grixba' and 'Play Ransomware' in its context, suggesting it targets behaviors associated with these threats.
This rule looks for a Rust-based stealer that uses Tor for hiding traffic and low-level Linux hooks associated with IronWorm. This malware targets developers through poisoned packages. Linux build servers are at special risk. Ask the person who used the computer whether they installed new software or clicked a link, and involve your security team if the answer is unclear.
This rule identifies accounts that create or modify 10 or more files, each larger than 200MB, within a one-hour period. This behavior can be indicative of data exfiltration, staging of large files, or other suspicious bulk file operations.
Page 145 of 232