Scanning 7.6 Petabytes of HuggingFace Training Data for Secrets
6 hours ago
- A scan of 7.6 petabytes of public AI training data on Hugging Face found 221,303 live, unique credentials in 6,003 datasets.
- The highest-impact secret exposed 393 GB of PII, covering an estimated 3.7% of the global population.
- Supply chain risks include 349 live GitHub personal access tokens (223 with full repo write, 130 with CI workflow write, 112 with admin:org, 110 with package publishing) and 318 Docker Hub tokens that can push images.
- Live cloud credentials include 8,557 GCP service-account keys, 3,343 AWS keys passing STS identity checks, and 8,594 live database logins.
- 5,885 live Slack tokens and Mailgun keys were found, with examples from a Fortune 500 tech workspace and major brand domains.
- A live AWS key from a Brazilian fintech leaked via a chatbot conversation, captured and mirrored 18 times in the training data.
- At least 11,496 live AI provider keys (OpenAI, Azure, Anthropic, etc.) were found, with a potential minimum cost of $920,000 per year in stolen inference.
- Hugging Face tokens include 787 live ones (237 with write access, 70 with org-admin), with 63 self-leaks and 700 scraped from elsewhere.
- Leaks multiply: 44% of secrets appear in more than one dataset, with one key copied into 1,131 datasets.
- Named open models and corpora contain thousands of live keys, including StarCoder, OLMo 3, SmolLM2, and Huginn.
- Recommendations: scan before publishing, scan before training, rotate any key that touched a public surface, and enable leak alerts.
- Training data leaks are permanent; only rotation (revocation) neutralizes them.
- The scan was conducted with responsible disclosure to Hugging Face, who are also contributing storage bucket scanning support to TruffleHog.