Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
57 detections
Filters
Last updated
All Time
Detection languages
24
11
7
5
5
Contributors
24
10
5
3
3
Categories
30
24
13
12
9
Platforms
26
23
15
7
7
Products / Services
22
13
11
5
5
MITRE Techniques
18,115
15,635
12,576
8,388
6,215
IDS Classtypes
4
1
IDS Protocols
4
1
Detects modifications to Microsoft Entra ID (formerly Azure AD) cross-tenant access settings. This rule alerts on changes that allow external tenants to interact with the environment, such as enabling inbound/outbound trusts, automatic redemption, or trusting MFA claims, which can be leveraged to establish persistence or facilitate lateral movement between tenants.
Detects modifications to Microsoft Entra ID (formerly Azure AD) cross-tenant access settings. This rule alerts on changes that allow external tenants to interact with the environment, such as enabling inbound/outbound trusts, automatic redemption, or trusting MFA claims, which can be leveraged to establish persistence or facilitate lateral movement between tenants.
This rule monitors for unauthorized changes to GitHub Actions workflows that involve release or publishing processes, specifically looking for indicators of supply chain compromise like the introduction of 'id-token: write' or changes to publish scripts. It correlates these modifications with subsequent workflow executions and npm registry publish events attributed to the same actor to identify potential account takeover and malicious package distribution.
Detects potential SaaS supply-chain attacks where a third-party application or connector triggers an OAuth permission scope escalation or publishes a new version, followed by the associated service account initiating outbound network connections to rare or newly-registered domains within a 24-hour window.
Monitors SaaS application integration service accounts (e.g., Salesforce connected apps) by establishing baselines for API call volume and accessed object types. The rule alerts on anomalous spikes in usage or deviations in the scope of accessed data objects, which could indicate the abuse of compromised OAuth tokens following a vendor supply-chain compromise.
Detects anomalous remote access patterns on a single endpoint, specifically involving AnyDesk or TeamViewer sessions originating from multiple distinct geographical locations combined with usage by multiple distinct user accounts. This pattern is consistent with DPRK IT worker fraud (Wagemole) involving shared laptop farms.
Detects anomalous remote access patterns on a single endpoint, specifically involving AnyDesk or TeamViewer sessions originating from multiple distinct geographical locations combined with usage by multiple distinct user accounts. This pattern is consistent with DPRK IT worker fraud (Wagemole) involving shared laptop farms.
Detects when a namespace-scoped identity creates, updates, or patches AWS or Azure IAM-related custom resources in Kubernetes. This pattern monitors for a 'confused deputy' scenario where a user might attempt to leverage high-privilege cloud operators (like ACK or ASO v2) that operate with a shared high-privilege identity to modify cloud IAM configurations.
Detects when a namespace-scoped identity creates, updates, or patches AWS or Azure IAM-related custom resources in Kubernetes. This pattern monitors for a 'confused deputy' scenario where a user might attempt to leverage high-privilege cloud operators (like ACK or ASO v2) that operate with a shared high-privilege identity to modify cloud IAM configurations.
Detects a suspicious runtime pattern in GitHub Actions where a runner environment installs the Bun runtime and immediately executes an action's index.js file. This pattern is characteristic of supply chain attacks where a compromised GitHub Action uses mutable-tag pinning to smuggle and execute an obfuscated JavaScript payload before legitimate action logic.
Detects when a namespace-scoped identity creates, updates, or patches AWS or Azure IAM-related custom resources in Kubernetes. This pattern monitors for a 'confused deputy' scenario where a user might attempt to leverage high-privilege cloud operators (like ACK or ASO v2) that operate with a shared high-privilege identity to modify cloud IAM configurations.
Detects when a namespace-scoped identity creates, updates, or patches AWS or Azure IAM-related custom resources in Kubernetes. This pattern monitors for a 'confused deputy' scenario where a user might attempt to leverage high-privilege cloud operators (like ACK or ASO v2) that operate with a shared high-privilege identity to modify cloud IAM configurations.
Detects when a namespace-scoped identity creates, updates, or patches AWS or Azure IAM-related custom resources in Kubernetes. This pattern monitors for a 'confused deputy' scenario where a user might attempt to leverage high-privilege cloud operators (like ACK or ASO v2) that operate with a shared high-privilege identity to modify cloud IAM configurations.
Detects pull requests created in GitHub repositories by entities labeled as 'Bot', 'App', or 'integration', or containing the term 'codex', specifically targeting repositories where such entities have not performed these actions in the previous 30 days. This baseline approach identifies potentially hijacked or unauthorized automation accounts performing activities outside of their standard repository scope.
Detects pull requests created in GitHub repositories by entities labeled as 'Bot', 'App', or 'integration', or containing the term 'codex', specifically targeting repositories where such entities have not performed these actions in the previous 30 days. This baseline approach identifies potentially hijacked or unauthorized automation accounts performing activities outside of their standard repository scope.
Detects pull requests created in GitHub repositories by entities labeled as 'Bot', 'App', or 'integration', or containing the term 'codex', specifically targeting repositories where such entities have not performed these actions in the previous 30 days. This baseline approach identifies potentially hijacked or unauthorized automation accounts performing activities outside of their standard repository scope.
Detects pull requests created in GitHub repositories by entities labeled as 'Bot', 'App', or 'integration', or containing the term 'codex', specifically targeting repositories where such entities have not performed these actions in the previous 30 days. This baseline approach identifies potentially hijacked or unauthorized automation accounts performing activities outside of their standard repository scope.
Detects pull requests created in GitHub repositories by entities labeled as 'Bot', 'App', or 'integration', or containing the term 'codex', specifically targeting repositories where such entities have not performed these actions in the previous 30 days. This baseline approach identifies potentially hijacked or unauthorized automation accounts performing activities outside of their standard repository scope.
KQL Query from file: Hunting Mirage kitten AKA unc1549
Detects suspicious execution patterns associated with the SleeperGem supply chain attack, where a compromised Gem install script (git_credential_manager-2.8.3/bin/install) spawns shell or PowerShell commands to trigger secondary malicious scripts like deploy.sh or redirects output to /dev/null.
Detects successful Microsoft 365 user authentications where Conditional Access (CA) policies were bypassed, resulting in single-factor authentication. This pattern is indicative of attackers using compromised edge network appliances—which are often configured as trusted network locations—to proxy authentication requests and circumvent security controls.
Page 2 of 3