TBNTech
Claude Code is accidentally exposing secrets all over GitHub
Publication: Ars Technica - All content
Author: Kyle Orland
Source published: 09/11/2026, 17:24:26 UTC
Briefing created: 10/11/2026, 07:58:00 UTC
Based on a feed excerpt; full article content has not been acquired. Source evidence retrieved 09/11/2026, 18:13:24 UTC.
Briefings
AI security researchers at Apiiro discovered that Claude Code leaks sensitive data like database passwords and API tokens to GitHub via settings files. This occurs when users approve automated shell commands with 'Yes, and don't ask again', which are stored in .claude/settings.local.json and sometimes incorrectly included in .gitignore. Anthropic documents this behavior, but the leak persists because the file is not always properly ignored by Git. The incident highlights a gap between user consent and automated command execution.
Key points
- Apiiro researchers identified thousands of secrets including database passwords and API tokens leaked via Claude Code settings files.
- The leak occurs when users approve automated shell commands with 'Yes, and don't ask again', which are stored in .claude/settings.local.json and sometimes incorrectly included in .gitignore.
Context
Anthropic documents that .claude/settings.local.json is added to .gitignore, but the actual leak persists because the file is not always properly ignored by Git. This finding matters as it reveals a gap between user consent and automated command execution.
Limitations
Evidence is limited to a single incident reported by Apiiro researchers; no specific dates or locations are confirmed. The leak persists because the file is not always properly ignored by Git, but the exact mechanism of failure is not fully explained. No specific numbers of leaked secrets are confirmed beyond 'thousands'. No public consequences are documented.
Generated by Bittrees-hosted qwen35-2b sha256:aaf42c8b7c3c on 10/11/2026, 07:58:00 UTC. Based on publisher-provided feed evidence; may not cover the full original article. Check the source for details.
View archived briefing on IPFS
bafybeicpyuql5g2do2lurhifnn44qyypesfuqgxbx2p4ntekekdm5qaduq