Cases › leaked private data › LR-2026-0863
Claude Code approval rules exposed credentials in public GitHub repositories (Apiiro research)
- Who was hit
- 1,122 public configuration files across 1,994 repositories; 63 organisations, primarily software companies; 2,539 secrets including database passwords, SSH credentials, GitHub/GitLab/npm tokens and AWS keys
- AI agent used
- Claude Code
- AI company and model
- Anthropic · Claude Code
- Money lost or records
- 2,539 records
- Other parties hit
- 63
- How it was found
- Third party
- Reported
- 7 Nov 2026
- Severity
- Major
- Tools it had
- shell
- Sector
- Professional, Scientific, and Technical Services
- Claude Code, Anthropic's AI coding assistant, ran shell commands for developers after approval and saved those approvals as rules in .claude/settings.local.json.
- Some approval rules stored the complete command in plaintext, so passwords, API keys and tokens entered in commands were written into the settings file, which could then be committed to public repositories.
- The secrets reached public GitHub: 1,122 files with at least one secret, and 2,539 secrets across 1,994 repositories including history and saved conversations, belonging to 63 organisations.
- Cybersecurity firm Apiiro found the exposures in its investigation of public GitHub repositories.
Source: The 420.in · 9 more
What was done
Apiiro advised rotating exposed credentials before removing files, using repository-level .gitignore rules, checking history, and using environment variables or secret managers. No exploitation was confirmed.
Monitoring added (Researcher or third party) · Monitoring added (Researcher or third party)
Advice in source, not a fix by the party: “Apiiro advised rotating exposed credentials before removing files, using repository-level .gitignore rules, checking history, using environment variables or secret managers, and extending scanning to AI assistant config folders.”
Risks Privacy harm to a person (42 incidents)
No source states: company using the AI.
Similar incidents
Evidence
- Records exposed 2,539
- Other parties affected 63
- Cause a safeguard that was in place did not hold
Sources (10)
- Claude Code Permission Feature Exposes 2,539 Secrets Across GitHub Repositories - The 420.in · The 420.in · 2026-11-07
- Claude Code's "Don't Ask Again" Feature Exposes 2,539 Secrets Across 1,994 GitHub Repositories · GBHackers News · 2026-11-07
- TechFlow Intel: ChatGPT Exposed for Mass Account Bans, Binance CFO Resigns Swiftly After $6 Billion Cyberattack · 深潮TechFlow · 2026-11-08
- Claude Code’s “Don’t Ask Again” Feature Linked To Public Exposure of Developer Credentials · LinkedIn · 2026-11-08
- Apiiro: Claude Code 'Don't Ask Again' Leaks Keys in 1,122 Repos | AI Weekly · AI Weekly · 2026-11-08
- Claude Code is accidentally exposing secrets all over GitHub · Ars Technica · 2026-11-09
- Claude Code leaks over 1,300 secrets into public GitHub repositories · Crypto Briefing · 2026-11-09
- Claude Code Secrets Leak to GitHub via 'Don't Ask Again' · ShiftDelete.Net · 2026-11-10
- 2,539 secrets in 1,994 public repos: How an AI coding agent’s ‘don’t ask again’ button exposed enterprise credentials - Express Computer · Express Computer · 2026-11-11
- "Don't ask again": how AI coding agents publish developers' passwords · Cybersecurity Insiders · 2026-11-14
Show every field, with its source and grade
The AI system
What happened
Impact
Context
LR-2026-0863 · version 16 · published 2026-11-15 after automatic checks; not yet checked field by field by a person