GitHub Repository Exfiltration Campaign Using Compromised PATs
GitHub Repository Exfiltration Campaign Using Compromised PATs is a high-severity credential theft issue in Organizations with exposed/compromised classic GitHub PATs, an AI agent. Affected: Organizations with exposed/compromised classic GitHub PATs.
Is Organizations with exposed/compromised classic GitHub PATs running on your developers' machines? Anomity finds every device with this AI agent installed, shows the version, and can block it by policy. Detect this across your developers' devices with Anomity →
Key facts
- ID
github-repository-exfiltration-campaign-using-compromised-pats- Severity
- high
- Attack type
- Credential theft
- Component
- Organizations with exposed/compromised classic GitHub PATs · AI agent
- Known exploited
- No known exploitation
- Published
- Last verified
What is this vulnerability?
Wiz Research identified an active campaign in which a threat actor used compromised GitHub Personal Access Tokens (classic) for mass repository cloning, API-based reconnaissance, low-volume test cloning, then large-scale parallel exfiltration from dedicated cloud infrastructure. Source code and embedded secrets are the prize.
Affected versions
| Affected | Fixed in |
|---|---|
Organizations with exposed/compromised classic GitHub PATs | No fixed version listed |
Am I affected by this vulnerability?
You are affected if you run Organizations with exposed/compromised classic GitHub PATs.
How do I fix it?
Rotate classic PATs and migrate to fine-grained, short-lived tokens with least-privilege scopes. Enforce SSO + IP allowlisting on the org, and review audit logs for anomalous clone volume.
How do I find every machine running Organizations with exposed/compromised classic GitHub PATs?
Anomity inventories the AI agents, MCP servers, IDE extensions and skills on each developer device, so you can see which machines run Organizations with exposed/compromised classic GitHub PATs and which version, then enforce a policy on it.