The distilled version
- Security researchers at Apiiro found over 100,000 Claude Code settings files uploaded to public GitHub repos, with about 1,100 of them containing real secrets like database passwords and API keys.
- The leak happens because a local settings file can store commands with sensitive data in them, and that file sometimes gets uploaded by accident when a repo is cloned or created.
- If anyone on your team uses Claude Code, check your GitHub repos for this settings file and rotate any exposed credentials.
What happened
Ars Technica reports that AI security firm Apiiro found thousands of secrets, including database passwords, API tokens and root logins, sitting inside Claude Code settings files that had been uploaded to public GitHub repositories.
The issue stems from how Claude Code stores a user’s approval to run a shell command without asking again: that approval is saved in a local file called .claude/settings.local.json, often along with the exact command, secrets and all. Anthropic’s documentation says this file should be excluded from sharing by a global setting, but that protection doesn’t always carry over at the repo level, so the file can end up public if a repo is cloned or a folder later becomes a repo. Apiiro says Claude Code itself sometimes commits changes to this file without the user asking it to.
Apiiro found over 100,000 of these settings files on public GitHub, with about 1,100 from 63 organizations containing exposed secrets. Claude Code’s Boris Cherny said on Hacker News that the team is looking into fixes and recommends using secret scanners, though Apiiro found that two popular scanners missed 215 of the secrets it discovered. Bug reports flagging this problem go back to August 2025 but were closed without action.
Why it matters
If anyone in your business uses Claude Code to write or maintain software, including a contractor or freelance developer, a leaked settings file could expose passwords, API tokens or root logins to the open internet. That’s not a hypothetical: real organizations have already had secrets like this exposed.
What it means for your business
If you run the business: ask whoever manages your website, app or internal tools whether they or any contractor uses Claude Code. If so, get them to check public GitHub repos for a file called .claude/settings.local.json and rotate any credentials found there.
What to do
Act now- Ask any developer working with your code, including contractors, whether they use Claude Code.
- Search your public and private GitHub repos for .claude/settings.local.json.
- If the file turns up with real secrets inside, rotate those passwords, keys and tokens immediately.
- Check forks of your repos, not just the main one, since old secrets can persist there even after cleanup.
- Ask developers to run a secret scanner on their repos, but don’t assume it will catch everything.
Act now: worth doing this month.
Jargon in this story
Sources
- 1Claude Code is accidentally exposing secrets all over GitHub (opens in a new tab) · Ars Technica · News report · Nov 9, 2026