# github-repository-exfiltration-campaign-using-compromised-pats: 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.

- **Canonical URL:** https://catalog.anomity.ai/vuln/github-repository-exfiltration-campaign-using-compromised-pats
- **Aliases:** ti-043
- **Severity:** high
- **Attack type:** Credential theft
- **Component:** Organizations with exposed/compromised classic GitHub PATs (AI agent)
- **Exploited in the wild:** no known exploitation
- **Published:** 2026-06-03
- **Last verified:** 2026-11-01
- **JSON:** https://catalog.anomity.ai/api/entries/vuln/github-repository-exfiltration-campaign-using-compromised-pats

## Summary

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.

## References

- article: https://www.wiz.io/blog/github-attacks-pat-control-plane

## Related vulnerabilities

- [opencode-console-breach-saved-openai-anthropic-and-google-provider-keys](https://catalog.anomity.ai/vuln/opencode-console-breach-saved-openai-anthropic-and-google-provider-keys) — high
- [symantec-the-aoki-infostealer-now-takes-claude-codex-cursor-copilot](https://catalog.anomity.ai/vuln/symantec-the-aoki-infostealer-now-takes-claude-codex-cursor-copilot) — high
- [manus-one-email-with-a-jsfuck-payload-or-one-shared-project-instruction](https://catalog.anomity.ai/vuln/manus-one-email-with-a-jsfuck-payload-or-one-shared-project-instruction) — high
- [GHSA-wp6x-29qx-fpr7](https://catalog.anomity.ai/vuln/ghsa-wp6x-29qx-fpr7) — high
- [mandiant-hijacked-ai-coding-assistant-session-deploys-shai-hulud-across](https://catalog.anomity.ai/vuln/mandiant-hijacked-ai-coding-assistant-session-deploys-shai-hulud-across) — critical
- [anthropic-september-2026-threat-report-fake-claude-code-installers-and](https://catalog.anomity.ai/vuln/anthropic-september-2026-threat-report-fake-claude-code-installers-and) — high

---

Source: Anomity Security Database (https://catalog.anomity.ai/vuln). Detect affected AI tools on developer devices: https://anomity.ai/?utm_source=catalog&utm_medium=vuln-md&utm_campaign=github-repository-exfiltration-campaign-using-compromised-pats