GitHub Exfiltration via High Number of Repository Clones by User
Detects a high number of repository cloning actions by a single user within a short time frame. Adversaries may clone multiple repositories to exfiltrate sensitive data.
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
- ESXiIaaSLinuxmacOSNetwork DevicesOffice SuiteSaaSWindows
The rule states no platform. This is derived from the 3 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
- 19f3674c-f4a1-43bb-a89c-e4c6212275e0
- Tagged by the source as
- Data Source: GithubData Source: GitHub Audit LogsDomain: CloudDomain: SaaSNoise: MediumPerformance: FastPlatform: GitHubResources: Investigation GuideRule Type: ES|QLTactic: ExfiltrationUse Case: Threat Detection
Licence
- Published under
- Elastic License 2.0Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Sep 20, 2026
- Version
- 3