Gheist: GitHub tokens stolen

GitHub

Ongoing supply chain attack harvests credentials and sensitive data from thousands of developer repositories

Do this now

Revoke and rotate any GitHub tokens and secrets that were ever stored in your repositories.

First seen: 26 Oct 2026
Last update: 26 Oct 2026, 18:01 UTC
Source: news

Check this repository for exposure to one security incident from pwned.coffee. Report first, change nothing until I say so.

## Gheist: GitHub tokens stolen
Severity: unknown. Patch status: no fix yet.
Affected: GitHub

Ongoing supply chain attack harvests credentials and sensitive data from thousands of developer repositories

## Steps
1. Search the repo, its CI and infra config for GitHub. If present, report the version in use and whether it's affected.
2. There is no fix yet. Until one ships: restrict network access to it.

## Report
A table: file, product or package, version in use, affected yes/no, exact fix. Then anything a human has to check outside the repo.

If you have the pwned.coffee MCP server (https://pwned.coffee/mcp), call lookup_cve for the latest, and check_repo with this repo's lockfiles, Dockerfiles and workflows for a full receipt.
Sources: https://www.darkreading.com/cyberattacks-data-breaches/gheist-stolen-github-tokens-cloud-secrets
https://pwned.coffee/i/gheist-github-tokens-stolen

Receipt

Exploitation: No known exploitation
Score: No CVSS published yet: severity unknown.
Last checked: 26 Oct 2026, 19:18 UTC

Sources: KEV – CVE record – Vendor –

Sources

darkreading.com: 'Gheist' Weaponizes GitHub Tokens to Steal Cloud Secrets

Wrong fix version, or a source we missed? Send it back to chef@pwned.coffee with the source, and we'll correct it here.

Totalone coffee