Wiz Details Investigation Playbook for GitHub PAT Theft and Repository Exfiltration

Summary
Wiz describes a multi-organization campaign using stolen GitHub PATs for repository reconnaissance and mass cloning, and outlines how responders can contain tokens, trace activity, assess exposed secrets and data, rotate credentials, and hunt for follow-on misuse.
Key points
- Wiz CIRT investigated a campaign active from mid-May to early June 2026 that used valid employee PATs across multiple organizations.
- The activity progressed from repository reconnaissance on May 15, to low-volume cloning from May 29–31, and mass cloning on June 1.
- The June 1 activity used 102 AWS IP addresses in ca-central-1 and the git/2.43.0 user agent to clone as many as thousands of repositories per organization.
- Wiz did not identify how the PATs were exposed; endpoint compromise is considered possible but was not confirmed.
- Responders should revoke or remove token access where possible, temporarily restrict affected users, and investigate potential endpoint or credential-store compromise.
- The playbook recommends reviewing GitHub audit and user security logs, identifying cloned repositories, checking for exposed secrets and sensitive data, rotating credentials, and hunting for unauthorized use.
- GitHub Enterprise Cloud retains git.clone, git.fetch, and git.push events for only seven days; earlier reconnaissance API requests may require Enterprise Log Streaming for visibility.
Article Details
- Defense Focus
- Investigate and contain compromised GitHub Personal Access Tokens (PATs), establish the scope of repository access and exfiltration, identify exposed secrets and sensitive data, and hunt for subsequent credential misuse.
- Detection Methods
- Baseline users' normal GitHub activity, including source IPs, geolocations, user agents, access times, and repository activity; investigate anomalies tied to the compromised PAT or user.
- Review GitHub audit logs, personal GitHub security logs, and enterprise audit logs; use Enterprise Log Streaming to investigate api.request events that standard audit logs may not contain.
- Pivot on reported source IPs and user agents to identify related activity, and correlate GitHub events with cloud control-plane events.
- Identify all repositories cloned using relevant IOCs, then inspect them for exposed credentials and sensitive data.
- Search cloud, SaaS, and internal services for unauthorized use of exposed credentials before and after rotation.
- Data Sources
- GitHub audit logs, including git.clone, git.fetch, and git.push events
- GitHub personal security logs
- GitHub enterprise audit logs and Enterprise Log Streaming api.request events
- Cloud provider control-plane logs
- Repository contents and Wiz Secret Findings and Data Findings
- Rule Types
- Wiz Defend Threat Detection Rules for mass private-repository cloning, cloning from low-reputation IPs, unusual PAT use, repository enumeration, unusual repository access, automated high-volume activity, and workflow-log deletion
- Platforms
- GitHub
- Wiz
- Defensive Actions
- Revoke or remove organization access for the compromised PAT according to its type and the organization's identity configuration; ask the affected user to delete classic PATs when necessary.
- Temporarily remove the affected user from the organization while investigating, and consider restricting access to other sensitive systems and isolating potentially affected endpoints.
- Determine how the PAT was exposed and whether additional credentials may have been exposed.
- Identify every repository cloned and assess its secrets and sensitive data; treat valid secrets in exfiltrated repositories as potentially compromised.
- Document credential identifiers, affected services, and rotation times, then rotate exposed credentials promptly.
- Hunt for unauthorized use of exposed credentials across cloud providers, SaaS platforms, and internal services.
- Stream GitHub enterprise audit logs and cloud provider logs to a centralized system; account for GitHub Enterprise Cloud's seven-day retention of Git events.
Indicators of compromise
| Type | Indicator | Context |
|---|---|---|
| IPV4 | 107[.]174[.]201[.]183 | Source IP listed as a network IOC and used for low-volume repository-cloning validation. |
| IPV4 | 13[.]221[.]167[.]217 | Source IP listed as a network IOC and used for GitHub API reconnaissance. |
| IPV4 | 15[.]157[.]62[.]127 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 15[.]157[.]63[.]171 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 15[.]157[.]65[.]4 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 15[.]157[.]68[.]0 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 15[.]157[.]69[.]80 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 15[.]157[.]70[.]253 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 15[.]222[.]60[.]246 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 15[.]222[.]60[.]27 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 15[.]222[.]61[.]83 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 15[.]222[.]64[.]207 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 15[.]223[.]121[.]133 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 15[.]223[.]186[.]60 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 15[.]223[.]188[.]87 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 15[.]223[.]199[.]223 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 15[.]223[.]2[.]184 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 15[.]223[.]200[.]124 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 15[.]223[.]204[.]99 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 15[.]223[.]206[.]124 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 15[.]223[.]207[.]112 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 15[.]223[.]63[.]237 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 15[.]223[.]65[.]175 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 15[.]223[.]67[.]252 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 15[.]223[.]74[.]214 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 15[.]223[.]74[.]59 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 16[.]52[.]128[.]252 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 16[.]52[.]147[.]129 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 16[.]52[.]147[.]249 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 16[.]52[.]166[.]75 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 16[.]52[.]169[.]32 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 16[.]52[.]37[.]91 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 16[.]52[.]40[.]180 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 16[.]52[.]50[.]245 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 16[.]52[.]76[.]162 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 16[.]52[.]82[.]13 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 16[.]52[.]86[.]223 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 16[.]54[.]241[.]145 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 16[.]54[.]241[.]240 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 16[.]54[.]243[.]226 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 16[.]54[.]253[.]67 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 3[.]96[.]127[.]99 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 3[.]96[.]138[.]214 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 3[.]96[.]141[.]125 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 3[.]96[.]142[.]210 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 3[.]96[.]149[.]105 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 3[.]96[.]173[.]139 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 3[.]96[.]173[.]8 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 3[.]96[.]187[.]238 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 3[.]96[.]193[.]166 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 3[.]96[.]197[.]212 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 3[.]96[.]199[.]215 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 3[.]96[.]200[.]150 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 3[.]96[.]201[.]161 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 3[.]96[.]208[.]217 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 3[.]96[.]210[.]47 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 3[.]96[.]210[.]9 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 3[.]96[.]218[.]171 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 3[.]97[.]11[.]39 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 3[.]99[.]161[.]201 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 3[.]99[.]171[.]218 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 35[.]182[.]104[.]189 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 35[.]182[.]13[.]97 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 35[.]182[.]157[.]210 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 35[.]182[.]17[.]157 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 35[.]182[.]176[.]228 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 35[.]182[.]213[.]73 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 35[.]182[.]251[.]252 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 35[.]182[.]78[.]22 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 35[.]182[.]79[.]86 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 35[.]182[.]83[.]50 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 35[.]183[.]106[.]137 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 35[.]183[.]111[.]110 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 35[.]183[.]112[.]105 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 35[.]183[.]121[.]31 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 35[.]183[.]126[.]121 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 35[.]183[.]129[.]254 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 35[.]183[.]136[.]221 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 35[.]183[.]15[.]41 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 35[.]183[.]178[.]163 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 35[.]183[.]20[.]241 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 35[.]183[.]210[.]27 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 35[.]183[.]235[.]214 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 35[.]183[.]236[.]91 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 35[.]183[.]243[.]11 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 35[.]183[.]26[.]57 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 35[.]183[.]34[.]62 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 35[.]183[.]42[.]203 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 35[.]183[.]64[.]193 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 35[.]183[.]65[.]4 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 35[.]183[.]69[.]26 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 52[.]60[.]229[.]238 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 99[.]79[.]128[.]151 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 99[.]79[.]128[.]234 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 99[.]79[.]161[.]206 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 99[.]79[.]189[.]128 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 99[.]79[.]193[.]97 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 99[.]79[.]32[.]153 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 99[.]79[.]33[.]200 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 99[.]79[.]48[.]16 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 99[.]79[.]52[.]86 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 99[.]79[.]64[.]18 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 99[.]79[.]72[.]217 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
| IPV4 | 99[.]79[.]75[.]249 | Source IP listed as a network IOC for the campaign's mass repository-cloning activity. |
MITRE ATT&CK
Vendors
GitHubOrganizations increasingly rely on GitHub to develop and store proprietary source code, internal documentation, and other software assets. This makes GitHub Personal Access Tokens (PATs) an attractive target forWizRecently, the Wiz Customer Incident Response Team (CIRT) investigated a coordinated campaign in which compromised GitHub PATs were used to conduct repository reconnaissance and mass repository exfiltration across
Products
GitHubOrganizations increasingly rely on GitHub to develop and store proprietary source code, internal documentation, and other software assets. This makes GitHub Personal Access Tokens (PATs) an attractive target forWiz Cloud EventsWiz customers can use the following Wiz Cloud Events query to retrieve activity conducted by a compromised PAT in order to identify anomalies. Additionally, use the Activity tab in the GitHub user’s drawer to seeWiz Data FindingsUse Wiz Data Findings with the repository Resource IDs from the CSV to determine which data may exist in these repositories:Wiz DefendWiz Defend includes Threat Detection Rules (TDRs) that detect suspicious and malicious activity across GitHub environments. Some of these rules reflect techniques observed in this campaign, while others provide broaderWiz GraphUse the following Wiz Graph query to search for Secret Findings associated with the compromised hashed_token.
