Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
2,431 detections
Filters
Last updated
All Time
Detection languages
2,428
3
Contributors
747
554
405
315
183
Categories
1,914
1,291
689
671
449
Platforms
2,202
183
149
62
49
Products / Services
2,366
1,378
38
37
25
MITRE Techniques
537
454
342
308
301
CVEs
17
10
9
9
9
IDS Classtypes
1,098
452
204
154
102
IDS Protocols
2,431
868
408
324
97
Detects outbound HTTP POST requests destined for 'aware-cr1.com' targeting the URI '/api/beacon', which is indicative of command-and-control (C2) communication associated with the 2CLoader malware.
This rule detects HTTP GET requests to a specific IP address (62.60.226.185) attempting to download a file named 't0907.exe'. This pattern is associated with the delivery phase of the 2CLoader malware.
This rule detects HTTP GET requests to a specific IP address (62.60.226.185) attempting to download a file named 't0907.exe'. This pattern is associated with the delivery phase of the 2CLoader malware.
This rule detects HTTP GET requests to a specific IP address (62.60.226.185) attempting to download a file named 't0907.exe'. This pattern is associated with the delivery phase of the 2CLoader malware.
Detects network activity associated with a malicious NPM package (typosquatting) beaconing to a known C2 server (69.48.229.140) and performing command and control operations, including command polling and data exfiltration, specifically from a Node.js environment.
Detects anomalous HTTP traffic directed to githubusercontent.com containing a custom, non-standard request header 'aohvcoehfg'. This pattern is associated with Kimsuky threat actor activity, specifically related to the 'GitPower' operation involving C2 communication via GitHub repositories.
Detects incoming HTTP requests to a FortiSandbox device that contain suspicious command injection patterns. The rule monitors both the URI and the request body for shell metacharacters such as ';', '|', '`', '$(', or '&&', followed by common binary execution commands (e.g., cat, wget, curl, bash, rm). This behavior is indicative of an exploit attempt targeting CVE-2026-39808.
Detects HTTP GET requests to network appliance management interfaces containing query parameters commonly used to trigger remote command or shell execution (e.g., cmd, exec, shell, command), which is characteristic of web shell activity.
Detects HTTP GET requests to the URI '/dpixel', which is a known default beacon URI pattern associated with the Brute Ratel C4 command and control framework's 'Badger' implant.
This rule detects malicious HTTP POST requests attempting a path traversal attack against Grav CMS, specifically targeting the __unique_form_id__ parameter. The rule looks for directory traversal sequences ('..') following the parameter, which is characteristic of attempts to read sensitive files outside the intended web directory.
Detects HTTP responses containing a file named 'ClaudeDesktop.exe' served from paths containing '/artifacts/' on the 'claude.ai' host where the request referrer is not 'claude.ai' or 'anthropic.com', suggesting a malvertising or supply chain delivery attempt of a malicious installer.
Detects network activity associated with the AMOS (Atomic macOS Stealer) malware, specifically identifying outbound HTTP POST requests to the '/api/t' URI path occurring on non-standard ports. The detection utilizes a threshold-based trigger to identify potential C2 communication heartbeats.
This rule detects network traffic patterns indicative of the Lumma Stealer 'ClickFix' phishing campaign. It identifies outbound requests to suspicious domains ending in .cyou utilizing specific user agents (WinHttp or Microsoft BITS), which are characteristic of malicious PowerShell scripts attempting to retrieve secondary payloads.
This rule detects HTTP POST requests to .php files containing suspicious PHP execution functions in the request body, such as 'system', 'eval', or 'shell_exec'. These patterns are indicative of an attempt to execute commands via an in-memory or injected PHP web shell on an F5 BIG-IP APM device.
Detects post-exploitation activity against Citrix NetScaler appliances associated with CVE-2026-8452. The rule specifically monitors for HTTP GET requests targeting PHP files within the /var/vpn/theme/ directory, accompanied by efforts to execute shell commands (bin/sh) via the web server.
Detects an exploitation attempt targeting SharePoint through the EditingPageParser by injecting a Register directive. This attempt involves bypassing SafeControls through specifically crafted HTTP POST requests to ToolPane.aspx, utilizing the GetPartPreviewAndPropertiesFromMarkup function to execute malicious tag patterns.
Detects two-stage phishing activity involving an initial visit to a Vercel-hosted lure page followed by the exfiltration or relay of fingerprinting and sandbox-evasion results to api.telegram.org.
Detects HTTP POST requests directed at common Machine Learning inference endpoints (e.g., /predict, /classify, /infer) where the request body claims to be a multipart form-data image upload (Content-Type: image/jpeg) but the actual binary data does not contain the standard JPEG file signature (FF D8 FF). This pattern is indicative of adversarial attempts to bypass security controls or provide malformed payloads to ML models.
Detects unauthenticated GET requests to known AI and machine learning infrastructure management endpoints (e.g., DCGM, Ray, Kubeflow) that are commonly exposed without authentication. These interfaces provide operational metrics, cluster status, or job management details, which can be leveraged for reconnaissance.
Detects outbound HTTP traffic to punycode-encoded domains (typically used to spoof legitimate sites) that contain characteristic boilerplate text often generated by LLMs in their responses. This combination is indicative of an automated phishing kit setup or a landing page generated by an AI assistant.
Detects unauthorized GET requests to common default paths associated with AI agent developer consoles and infrastructure, such as '/playground', '/api/predict', or '/_stcore'. These requests are identified by the absence of expected 'Authorization' or 'Cookie' headers, suggesting an unauthenticated probe or discovery attempt by an external actor looking for misconfigured or exposed AI development interfaces.
Page 12 of 116