High Number of Protected Branch Force Pushes by User
Detects a high number of force push actions to protected branches by a single user within a short time frame. Adversaries may perform force pushes to overwrite commit history on protected branches, potentially…
Description
Detects a high number of force push actions to protected branches by a single user within a short time frame. Adversaries may perform force pushes to overwrite commit history on protected branches, potentially leading to data loss or disruption of development workflows.
Detection logic
Its licence does not clear it for publishing here
Sunturai publishes a detection's own text where the licence it arrived under has been reviewed and permits it, and Elastic License 2.0 has not. The query as its source wrote it, its canonical form and the hash that pins this revision are in the workspace record.
Detection requirements
- Platform
- ContainersESXiIaaSLinuxmacOSNetwork DevicesOffice SuiteSaaSWindows
The rule states no platform. This is derived from the 4 ATT&CK techniques it maps to.
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| posthog.com/blog/nov-24-shai-hulud-attack-post-mortem | 7 |
| trigger.dev/blog/shai-hulud-postmortem | 7 |
| www.wiz.io/blog/shai-hulud-2-0-ongoing-supply-chain-attack | 17from 2 sources |
From the source
- At source
- Open at source
- Upstream identifier
- 0428c618-27f5-4d94-99e6-b254585aba69
- Tagged by the source as
- Data Source: GithubData Source: GitHub Audit LogsDomain: CloudDomain: SaaSNoise: LowPerformance: FastPlatform: GitHubResources: Investigation GuideRule Type: ES|QLTactic: ExfiltrationTactic: ImpactUse Case: Threat Detection
Licence
- Published under
- Elastic License 2.0Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Sep 20, 2026
- Version
- 3