Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
3,750 detections
Filters
Last updated
All Time
Detection languages
2,544
328
307
253
149
Contributors
953
720
641
297
173
Categories
1,245
994
880
773
476
Platforms
2,850
1,449
1,229
356
73
Products / Services
10,683
9,759
6,695
4,421
3,750
MITRE Techniques
1,096
989
950
912
820
CVEs
17
6
2
1
1
IDS Classtypes
9
4
3
2
2
IDS Protocols
21
1
Detects suspicious Microsoft Intune device enrollment activities characterized by the use of a spoofed User-Agent (matching Microsoft Office/Outlook strings) and rapid, multiple enrollment attempts within a short timeframe. This behavior is associated with adversary use of device-code phishing kits to enroll rogue devices using stolen session tokens.
Detects rapid rotation of multiple unique IP addresses originating from the same user account shortly after a device code authentication event. This behavior is indicative of threat actors using proxy rotation services (like FlashProxy) to obfuscate their origin and bypass location-based security controls or impossible-travel detections after hijacking a session.
Detects rapid rotation of multiple unique IP addresses originating from the same user account shortly after a device code authentication event. This behavior is indicative of threat actors using proxy rotation services (like FlashProxy) to obfuscate their origin and bypass location-based security controls or impossible-travel detections after hijacking a session.
Detects a successful user authentication event following a Microsoft OAuth 2.0 device authorization grant flow. This detection identifies scenarios where a user may have been phished into entering an attacker-supplied device code on a malicious Microsoft device login page, resulting in the attacker successfully obtaining OAuth tokens.
Detects anomalous device registration activity where a single user principal registers three or more distinct devices within a short duration (2 minutes). This behavior is characteristic of device-code phishing attacks where adversaries abuse stolen device authorization codes to register multiple rogue devices, potentially for PRT (Primary Refresh Token) acquisition.
Detects malicious OAuth 2.0 device authorization grant requests directed at Microsoft services. This rule identifies usage of specific App IDs associated with the Microsoft Authentication Broker combined with the 'offline_access' Graph scope, a pattern indicative of GhostCode-style phishing campaigns designed to steal access and refresh tokens.
Detects a suspected device code phishing (GhostCode) attack where a user authenticates via a device code flow, followed within 10 minutes by a non-interactive authentication request originating from a client utilizing the 'python-requests' user agent. This pattern is indicative of an adversary abusing a stolen device token to gain access to cloud resources.
This rule detects activities associated with the GhostCode phishing kit, which leverages a device-code phishing flow. It identifies malicious URLs interacting with harvester APIs to retrieve codes, email-delivered lures containing specific phishing markers ('userCodeDisplay', 'Verified Enterprise'), and corresponding endpoint/browser telemetry showing the rendered phishing page elements.
Detects anomalous device registration or Intune enrollment activity where a single user principal name (UPN) is associated with three or more distinct source IP addresses performing registration actions within a 90-second window. This behavior is indicative of automated, rapid rogue device registration campaigns aiming to bypass conditional access policies or establish unauthorized persistence.
Detects inbound emails containing keywords associated with known ransomware extortion tactics (e.g., mention of specific ransomware names, data leaks, and payment demands). The rule filters for inbound traffic to identify external threats while excluding potential internal-generated traffic.
This rule monitors network connections, DNS resolutions, and email URLs to detect traffic communicating with a known adversary-in-the-middle (AiTM) phishing infrastructure panel. By correlating security logs, DNS events, and email URL data against this specific indicator of compromise, it identifies potential interaction with phishing sites designed to capture credentials or session tokens.
Detects interaction with known infrastructure associated with the PREY-0058 campaign, which utilizes Adversary-in-the-Middle (AiTM) phishing lures mimicking passkey or MFA registration pages to target Microsoft 365 and other SaaS applications.
This rule detects email activity involving DocuSign-themed messages that contain attachments and also coincide with URL click events that redirect users to Microsoft-related login portals (e.g., login.microsoftonline.com or teams.microsoft.com) containing 'redirect' or 'redirect_uri' parameters. This behavior is indicative of a phishing attempt designed to capture credentials or perform OAuth consent phishing by mimicking legitimate document-signing workflows.
Detects active phishing threat-intelligence indicators whose domain name uses one of the disposable TLDs observed across IronToll's 73+ rotating lookalike domains (.cfd, .sbs, .icu, .buzz, etc.). Scoped to the structured ThreatType classification only — dropped the free-text 'Description has phishing' fallback, since KQL's 'has' is a substring/token match with no negation awareness (e.g. a description stating an indicator is 'not related to phishing' would still match), which could pull in indicators unrelated to actual phishing activity.
Detects emails delivering links to IronToll government-impersonation traffic-fine/payment portals (Egyptian and Moroccan justice-ministry lures), correlated with Safe Links click-through telemetry for the same URLs.
This rule identifies potentially compromised Entra ID accounts by correlating multiple suspicious behaviors within a 14-day window. It aggregates four specific indicators: successful authentication following repeated MFA failures, impossible travel (sign-ins from multiple countries within a short timeframe), unusual hour logons (00:00-05:00), and sign-ins flagged with medium/high risk or reported as compromised. The rule triggers when an account exhibits two or more of these distinct anomalous behaviors.
This rule identifies emails containing URLs associated with known suspicious or malicious domains (secboxes.com, msbenefit.com, attcdn.com, brianwilli.com). It filters for instances where the sender's domain is not one of the identified suspicious domains to reduce noise from potential email spoofing or miscategorized communications, flagging potential phishing attempts.
Detects rapid, successive successful interactive sign-ins for the same user account that each satisfy MFA requirements, but originate from geographically and technically distinct environments (different IP locations, ASNs, and device IDs) within a 2-minute window. This behavior is indicative of session hijacking via Adversary-in-the-Middle (AiTM) or Phishing-as-a-Service (PhaaS) frameworks.
Detects a high volume of subscription or account confirmation emails directed at a single recipient within a one-hour window. This behavior, often referred to as 'email bombing,' can be used to disrupt user productivity, overwhelm inbox capacity, or serve as a distraction technique to hide other malicious activities, such as spearphishing or account takeover notifications.
Detects anomalous data access or collection activity across multiple M365 workloads (SharePoint, OneDrive, Exchange). The rule identifies users exhibiting high volumes of file or mail access across at least two distinct workloads within a one-hour window, which may indicate account compromise, bulk data exfiltration, or unauthorized persistence via mailbox rules.
This rule monitors Office 365 activity for anomalous search behavior, specifically targeting high volumes of distinct search queries involving site collections, web structures, or index ID patterns. Such patterns are indicative of automated data discovery or enumeration activities performed against SharePoint or OneDrive environments.
Page 72 of 179