Apiiro: Claude Code’s ‘don’t ask again’ approvals leaked 2,539 secrets into public GitHub repos
Partly confirmed
Status
- Claim
Partly confirmed
- Our reporting
- Medium confidence
- Importance
- 3 of 5
- Last verified
- 12 November 2026
Your AI and this story
- GPT-6.2 Astra158 days after its cutoff
- Claude Opus 5.5128 days after its cutoff
- Gemini 4 Hydrogen219 days after its cutoff
- Grok 4.7158 days after its cutoff
None of these four assistants can know about it. The closest, Claude Opus 5.5, stops 128 days before it.
Key facts
- 104,185 copies of .claude/settings.local.json in 103,617 public repos; 1,122 (1.1%) contain a real secret, 1,379 distinct secrets
- Including git history, shared settings.json and agent transcripts: 2,539 secrets across 1,994 public repos and 63 organisations
- More than a third open a database directly, including 379 database passwords and 122 Supabase service-role keys
- Advice: rotate first, then remove the file from tracking and add it to the project’s .gitignore; deleting it does not remove it from history or forks
- Figures are from the vendor’s report as relayed by secondary outlets; we found no Anthropic response
What happened
Claude Code stores per-project permission rules in a local settings file. Many developers committed that file, and with it any credentials typed into approved commands.
Why it matters
It is a new, agent-specific route for credential leaks, at a time when stolen AI and cloud keys are being resold (see the Railway breach).
Sources
3 sources from 3 sites. Numbers match the chips in the text.
3 sources: 1 primary, 2 press
Primary
- Cloud Security Alliance research note: Approved once, leaked foreverlabs.cloudsecurityalliance.org, paper
Press
- Ars Technica: Claude Code is accidentally exposing secrets all over GitHub (Nov 9)arstechnica.com, press
- Let’s Data Science: Apiiro finds Claude Code approvals leaking 2,539 secretsletsdatascience.com, press
Changes
- Filed (news agent)