Response playbooks, investigation guides, and Atomic Red Team tests are Pro-only. Upgrade to unlock the full detection package for THREAT-CodeRepo-GistExfil.
Upgrade to ProDetect Data Exfiltration via GitHub Gists and Private Code Repositories in Google Chronicle
Adversaries and malicious insiders increasingly use code-hosting platforms (GitHub, GitLab, Bitbucket) as covert exfiltration channels because traffic to these domains is rarely blocked by web proxies and blends with routine developer activity. Two distinct abuse patterns are observed: (1) anonymous or throwaway-account Gist/paste creation used as a low-friction dead drop for small stolen artifacts (credentials, config files, session tokens) — documented in Turla dead-drop resolver infrastructure and multiple commodity loader families that stage stolen data via the GitHub Gist API before onward retrieval; and (2) bulk exfiltration via `git push` or GitHub API PUT/POST calls to a personal or attacker-controlled repository, seen in APT41 intrusions abusing developer tooling and in Lazarus Group operations staging stolen source code and credentials on GitHub/GitLab ahead of retrieval. The same channel is a leading insider-threat vector: departing employees push proprietary source code or customer data to a personal GitHub account under the cover of routine commits. Detection must distinguish these from the overwhelming volume of legitimate CI/CD and developer git traffic, so the strongest signals are (a) git remotes that do not match the organisation's registered GitHub/GitLab organisation, (b) anonymous Gist creation (no owning account, effectively unlisted/unattributable), and (c) API calls using PUT/POST verbs against content endpoints from processes other than the organisation's recognised CI/CD runners.
MITRE ATT&CK
- Tactic
- Exfiltration
YARA-L Detection Query
rule code_repository_data_exfiltration {
meta:
author = "df00tech"
description = "Detects data exfiltration via git push to non-corporate remotes and Gist/Contents API abuse"
severity = "MEDIUM"
mitre_attack_tactic = "Exfiltration"
mitre_attack_technique = "T1567.001"
threat_actors = "Turla, APT41, Lazarus Group"
reference = "https://attack.mitre.org/techniques/T1567/001/"
events:
$e.metadata.event_type = "PROCESS_LAUNCH"
(
(re.regex($e.target.process.file.full_path, `(?i)git(\.exe)?$`)
and re.regex($e.target.process.command_line, `(?i)push`)
and re.regex($e.target.process.command_line, `(?i)(github\.com|gitlab\.com|bitbucket\.org)`))
or (
re.regex($e.target.process.file.full_path, `(?i)(curl|powershell|pwsh|python)(\.exe)?$`)
and re.regex($e.target.process.command_line, `(?i)api\.github\.com/gists`)
)
or (
re.regex($e.target.process.file.full_path, `(?i)(curl|powershell|pwsh|python)(\.exe)?$`)
and re.regex($e.target.process.command_line, `(?i)(api\.github\.com|api\.gitlab\.com|api\.bitbucket\.org)`)
and re.regex($e.target.process.command_line, `(?i)(/contents/|/repos/)`)
)
)
$hostname = $e.principal.hostname
condition:
$e
}Chronicle YARA-L 2.0 rule matching PROCESS_LAUNCH UDM events to detect exfiltration via code repositories. Fires on git push commands referencing GitHub/GitLab/Bitbucket, scripting-engine calls to the Gist API, and direct Contents/Repos API calls. Tune the git-push branch against your organisation's registered namespace using a Chronicle reference list for lower noise.
Data Sources
Required Tables
False Positives & Tuning
- Open-source contribution workflows pushing to external forks — maintain a Chronicle reference list of approved external namespaces and add a NOT re.regex(...) exclusion
- DevRel/security research Gist publishing — suppress via a reference list of approved principal.user.userid values
Other platforms for THREAT-CodeRepo-GistExfil
Testing Methodology
Validate this detection against 2 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.
- Test 1Simulate Exfiltration via Anonymous GitHub Gist
Expected signal: Sysmon Event ID 1: curl.exe process creation with command line referencing api.github.com/gists and a POST body.
- Test 2Simulate Exfiltration via Git Push to Non-Corporate Remote
Expected signal: Process creation events for git with 'push' in the command line and a remote URL not matching the corporate org.
Unlock playbooks & atomic tests with Pro
Get the full detection package for THREAT-CodeRepo-GistExfil — response playbook and atomic red team tests, plus investigation guidance and hunting queries.
df00tech Pro — £29/user/month