Loading AttackTrace...
Loading AttackTrace...
Exfiltration to Code Repository (T1567.001) is a MITRE ATT&CK technique associated with Exfiltration . Adversaries may exfiltrate data to a code repository rather than over their primary command and control channel.
Exfiltration to Code Repository (T1567.001) is a MITRE ATT&CK technique associated with Exfiltration. Adversaries may exfiltrate data to a code repository rather than over their primary command and control channel.
Attackers use Exfiltration to Code Repository because it provides a reliable way to advance their objective within the Exfiltration tactic, often with a favorable balance of impact versus detectability on ESXi, Linux, macOS, Windows environments. Defenders should assess this behavior in the context of the affected platform and adjacent activity rather than treating it as a standalone indicator.
Adversaries may exfiltrate data to a code repository rather than over their primary command and control channel. Code repositories are often accessible via an API (ex: https://api.github.com). Access to these APIs are often over HTTPS, which gives the adversary an additional level of protection.
Exfiltration to a code repository can also provide a significant amount of cover to the adversary if it is a popular service already used by hosts within the network.
No universal command represents Exfiltration to Code Repository. Capture the exact command line, arguments, parent process, account, host, and execution time from the investigated environment; do not operationalize unverified examples.
| Event ID | Log Channel | What It Indicates |
|---|---|---|
| Environment-specific | Relevant Windows channel(s) | Correlate authentication, process, object-access, and configuration events with the observed execution context. |
| Sysmon Event ID | Name | Why It's Relevant Here |
|---|---|---|
| Environment-specific | Validate configured telemetry | Use process, network, file, registry, DNS, or image-load telemetry only when relevant and enabled. |
No MITRE detection guidance published for this technique.
Relevant ATT&CK Data Sources: N/A
A universal Sigma rule would create unreliable results because this technique has no single guaranteed observable. Build detection logic from a documented behavior and supported data source, scope it to the affected platform, and validate it against benign administrative activity before deployment.
Start with the data sources named in the detection section. Scope searches by asset, identity, and time window; correlate the primary behavior with preceding access and subsequent actions. A portable query is intentionally not provided where the technique lacks a universal schema or observable.