Github Repository/Organization Transferred
Detects when a repository or an organization is being transferred to another location.
Detection logic
Detection requirements
- Platform
- IaaSLinuxmacOSNetwork DevicesOffice SuiteSaaSWindows
The rule states no platform. This is derived from the 2 ATT&CK techniques it maps to.
- Log source product
- github
- Log source service
- audit
Known benign triggers
- Allowed administrative activities.
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 |
|---|---|
| docs.github.com/en/enterprise-cloud@latest/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#migration | 4 |
| docs.github.com/en/migrations | Only this detection cites it |
| docs.github.com/en/organizations/managing-organization-settings/transferring-organization-ownership | Only this detection cites it |
| docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository | Only this detection cites it |
From the source
- At source
- Open at source
- Upstream identifier
- 04ad83ef-1a37-4c10-b57a-81092164bf33
- Tagged by the source as
- attack.exfiltrationattack.persistence
Licence
- Published under
- Detection Rule License 1.1Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Aug 26, 2026
- Version
- 1