Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
411 detections
Filters
Last updated
All Time
Detection languages
181
74
63
61
11
Contributors
113
62
55
52
32
Categories
140
133
102
96
49
Platforms
309
74
43
15
15
Products / Services
10,665
9,758
6,692
4,421
3,749
411
MITRE Techniques
126
125
81
72
64
CVEs
5
1
1
1
1
This rule detects GitHub Actions workflows that explicitly reference specific 'actions-cool' GitHub actions using a known-bad mutable version tag ('@v2.2.1'). This tag corresponds to malicious code introduced into these repositories, allowing for potential CI/CD pipeline poisoning and supply chain compromise.
This rule detects GitHub Actions workflows that explicitly reference specific 'actions-cool' GitHub actions using a known-bad mutable version tag ('@v2.2.1'). This tag corresponds to malicious code introduced into these repositories, allowing for potential CI/CD pipeline poisoning and supply chain compromise.
This rule detects GitHub Actions workflows that explicitly reference specific 'actions-cool' GitHub actions using a known-bad mutable version tag ('@v2.2.1'). This tag corresponds to malicious code introduced into these repositories, allowing for potential CI/CD pipeline poisoning and supply chain compromise.
Detects the use of specific malicious versions (v2.2.1) of GitHub Actions (actions-cool/issues-helper or actions-cool/maintain-one-comment) in workflow runs that also involve the exposure or referencing of the GITHUB_TOKEN, indicating potential credential theft and CI/CD pipeline compromise.
Detects the use of specific malicious versions (v2.2.1) of GitHub Actions (actions-cool/issues-helper or actions-cool/maintain-one-comment) in workflow runs that also involve the exposure or referencing of the GITHUB_TOKEN, indicating potential credential theft and CI/CD pipeline compromise.
Detects the use of specific malicious versions (v2.2.1) of GitHub Actions (actions-cool/issues-helper or actions-cool/maintain-one-comment) in workflow runs that also involve the exposure or referencing of the GITHUB_TOKEN, indicating potential credential theft and CI/CD pipeline compromise.
Detects a specific pattern indicative of malicious GitHub Actions reactivation. The rule identifies a workflow run that fails quickly (e.g., due to repository access issues) followed immediately by a successful run of the same workflow with a significantly longer duration. This behavior is consistent with resolving issues related to malicious actions-cool repository workflows.
Detects a specific pattern indicative of malicious GitHub Actions reactivation. The rule identifies a workflow run that fails quickly (e.g., due to repository access issues) followed immediately by a successful run of the same workflow with a significantly longer duration. This behavior is consistent with resolving issues related to malicious actions-cool repository workflows.
Detects a specific pattern indicative of malicious GitHub Actions reactivation. The rule identifies a workflow run that fails quickly (e.g., due to repository access issues) followed immediately by a successful run of the same workflow with a significantly longer duration. This behavior is consistent with resolving issues related to malicious actions-cool repository workflows.
Detects a specific pattern indicative of malicious GitHub Actions reactivation. The rule identifies a workflow run that fails quickly (e.g., due to repository access issues) followed immediately by a successful run of the same workflow with a significantly longer duration. This behavior is consistent with resolving issues related to malicious actions-cool repository workflows.
Detects a specific pattern indicative of malicious GitHub Actions reactivation. The rule identifies a workflow run that fails quickly (e.g., due to repository access issues) followed immediately by a successful run of the same workflow with a significantly longer duration. This behavior is consistent with resolving issues related to malicious actions-cool repository workflows.
Detects the suspicious reactivation of 'actions-cool/issues-helper' or 'actions-cool/maintain-one-comment' repositories within a known malicious window (September 14-19, 2026). These repositories were involved in the 'Mini Shai-Hulud' supply-chain attack. This rule identifies when previously disabled repositories are re-enabled or modified to become active, potentially re-exposing malicious release tags to downstream users.
Detects the suspicious reactivation of 'actions-cool/issues-helper' or 'actions-cool/maintain-one-comment' repositories within a known malicious window (September 14-19, 2026). These repositories were involved in the 'Mini Shai-Hulud' supply-chain attack. This rule identifies when previously disabled repositories are re-enabled or modified to become active, potentially re-exposing malicious release tags to downstream users.
Detects the suspicious reactivation of 'actions-cool/issues-helper' or 'actions-cool/maintain-one-comment' repositories within a known malicious window (September 14-19, 2026). These repositories were involved in the 'Mini Shai-Hulud' supply-chain attack. This rule identifies when previously disabled repositories are re-enabled or modified to become active, potentially re-exposing malicious release tags to downstream users.
This rule detects the creation of Git branches or tags using names that match the 40-character or 64-character hexadecimal format of Git commit hashes. This technique, identified in the context of Plugin4Shell, is used to spoof pinned-commit references, potentially misleading automated systems or developers into using malicious code versions.
Detects instances where a removed GitHub organization member performed bulk repository access (cloning or downloading) shortly before their removal, potentially indicating exploitation of retained access by a departed employee or an adversary using a valid account before deprovisioning. The rule identifies activity occurring more than 24 hours prior to removal involving multiple repositories or multiple access actions.
Detects modifications or creation of GitHub Actions workflow files containing references to Model Context Protocol (MCP) extensions or AI-related build tools. This monitors for indicators of potential software supply chain tampering, where an adversary injects unauthorized CI/CD pipeline steps for malicious execution.
Detects high-privilege administrative actions, such as adding collaborators, transferring repository ownership, generating personal access tokens, or pushing code, performed on GitHub repositories classified as 'plugin' types. This rule monitors for potential supply chain compromise or unauthorized access within plugin development workflows.
This rule detects potential CI/CD security compromises in GitHub by monitoring for modifications to workflow permissions that grant 'write-all' access, access to sensitive workflow secrets via 'pull_request_target' from forked repositories, and the registration of new self-hosted runners. These actions are common indicators of supply chain attacks aimed at poisoning pipeline execution or exfiltrating build secrets.
Detects an anomalous burst of git clone, fetch, or download events performed by a single GitHub user account against a large number of private repositories within a short timeframe (15-minute window). This pattern often indicates unauthorized bulk collection or exfiltration of sensitive source code by an actor using a valid account.
Detects Git force-push events or protected branch policy overrides on main or master branches where the authenticated GitHub user differs from the commit author or committer, and the commit is unsigned. This pattern is indicative of credential abuse or account compromise where an attacker pushes unauthorized code while masquerading as a project maintainer.
Page 5 of 20