Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
2,594 detections
Filters
Last updated
All Time
Detection languages
2,463
65
36
12
11
Contributors
991
707
594
140
61
Categories
2,159
1,453
1,273
576
444
Platforms
2,418
272
203
71
63
Products / Services
10,665
9,773
6,705
4,421
3,749
2,594
MITRE Techniques
808
512
383
246
210
CVEs
18
12
12
12
10
IDS Classtypes
1,144
447
282
188
105
IDS Protocols
1,378
413
318
209
34
This rule detects DNS queries and TLS SNI traffic directed towards identified phishing or malicious domains that mimic Passkey, Single Sign-On (SSO), or help desk authentication portals. These domains are commonly used by attackers for credential harvesting or adversary-in-the-middle (AiTM) phishing attacks targeting organizational authentication services.
This rule detects high-frequency network activity directed toward the Microsoft Graph API (graph.microsoft.com) utilizing the 'python-httpx' user agent. This pattern matches known exfiltration activity associated with Storm-3121/Storm-3032 threat groups, where automated scripts are used to move data out of the environment via legitimate cloud service APIs.
This rule monitors DNS queries and TLS SNI traffic for connections to domains that appear to be performing typosquatting, specifically targeting users by impersonating SSO and Passkey service providers. These domains mimic legitimate security portals to facilitate credential harvesting.
Detects high-frequency TLS sessions initiated from internal hosts to Microsoft identity, Graph API, and account management endpoints. This behavior often mimics legitimate interaction but may indicate an adversary rotating infrastructure, automating reconnaissance, or interacting with C2 channels disguised as legitimate SaaS traffic.
Detects DNS resolution requests for the domain 'myaccount.microsoft.com', which is the Microsoft account management portal. This activity is often associated with legitimate user authentication or account configuration processes, but can be used as part of reconnaissance or credential-related activities.
Detects DNS lookups and TLS SNI requests to known domains associated with Storm-3121 and Storm-3032 phishing campaigns. These campaigns utilize passkey or Single Sign-On (SSO) themed lures to facilitate credential harvesting.
Detection of DNS queries, TLS SNI, and HTTP Host headers matching domains associated with Storm-3121 and Storm-3032 phishing campaigns. These campaigns mimic identity, SSO, and passkey registration processes to capture credentials or perform token theft.
Detects network communication associated with Mantax Otax Android malware, including traffic to identified command-and-control (C2) infrastructure and attempts to retrieve dynamic configuration files from GitHub.
Detects HTTP POST requests targeting Cisco Firepower Management Center (FMC) that contain strings associated with internal service account processes or configuration files, indicative of an attempt to exploit CVE-2026-20316.
Detects unauthorized HTTP Basic authentication attempts targeting Cisco Firepower Management Center (FMC) using hardcoded service account credentials associated with CVE-2026-20316.
Detects outbound network traffic to the Telegram Bot API characteristic of malware command and control (C2). This rule specifically identifies Python-based requests using the 'python-requests' user agent performing common Telegram API operations (getUpdates, sendDocument, sendPhoto, getFile) typical of C2 frameworks like HEAVYGRAM or CHOSEN BRICK.
Detects network activity associated with the KREMLIN browser extension communicating with a known command and control domain (luizestrelhashapr.online). The rule monitors DNS queries, TLS SNI connections, and HTTP WebSocket upgrade requests to identify potential C2 communication.
Detects outbound HTTP GET requests to a specific C2 domain 'luizestrelhashapr.online' masquerading as CSS file fetches. The request pattern uses a specific path '/google_api/' followed by predefined alphanumeric filenames, consistent with the KREMLIN malware browser extension's C2 polling mechanism.
This rule detects outgoing HTTP requests to 'apimantax.otax.fun' attempting to initiate a WebSocket upgrade connection. This is characteristic of the Mantax Otax v2 malware family establishing a Command and Control (C2) channel.
This rule monitors HTTP POST requests for patterns indicative of armored malware (specifically StealC) beaconing to a Command and Control (C2) server. The rule looks for established connections that use POST requests while avoiding common patterns found in standard web traffic (like JSON, XML, or standard form data) and having a specific request body size threshold. The thresholding mechanism helps reduce noise by only alerting when multiple occurrences are observed within a short time frame, suggesting automated beaconing behavior.
Detects network indicators associated with 'ClickFix' social engineering campaigns. The rules identify connections to known malicious domains and IP addresses involved in serving fake CAPTCHA prompts or error-resolution instructions, as well as the delivery and subsequent transmission of specific overlay cookies ('cookie-captcha-complete') used in these attacks.
Detects outbound HTTP POST requests to a known StealC malware command-and-control (C2) endpoint. This rule monitors for established TCP connections and HTTP traffic directed towards a specific IP address associated with malicious exfiltration activity.
Detects outbound HTTP POST beaconing behavior to a known C2 IP address associated with the StealC malware and ClickFix campaign. This rule monitors for established connections to the hardcoded infrastructure used for exfiltrating data or receiving commands.
Detects network indicators associated with the StealC information stealer, including DNS lookups for identified C2 domains, HTTPS traffic to known C2 endpoints, and suspicious POST requests using multipart/form-data indicative of credential or session data exfiltration.
Detects outbound HTTP POST requests directed at a known StealC command-and-control IP address. The rule identifies suspicious beaconing behavior by looking for POST requests that lack a standard User-Agent, do not utilize common HTTP content types, and contain a request body exceeding 16 bytes, suggesting custom binary protocol usage.
Detects outbound HTTP POST requests directed at a known StealC command-and-control IP address. The rule identifies suspicious beaconing behavior by looking for POST requests that lack a standard User-Agent, do not utilize common HTTP content types, and contain a request body exceeding 16 bytes, suggesting custom binary protocol usage.
Page 70 of 124