Skip to content
Trending
BreakingLaptops & PCs2 min read

Claude Code install and CLI permissions leaked passwords at scale

The 'don’t ask again' setting saved time — and dumped passwords into public repos. Here’s how to find and fix it.

By Boot Sequence

The Computing Desk · (8 hours ago)

Reported fromoutlet, credited1
Photo via Notebookcheck

Claude Code’s 'don’t ask again' feature leaked 31,088 secrets across GitHub — including live database passwords, cloud keys and SSH credentials, before Anthropic patched it in version 2.1.323 on November 12, 2026. The flaw wasn’t theoretical: GitGuardian found 5,343 of those secrets were still active when detected. Most appeared in .claude/settings.local.json, a file Claude Code saves locally to remember shell command approvals, and one that, until the update, stored full commands in plain text, even if they contained tokens or passwords.

Anthropic’s own docs say the file should stay out of repositories. But its protection relied on being added to your local git excludes, not the project’s .gitignore. So it never travelled with the repo. Not to CI.

Not to teammates. Not to new machines. And not to Docker Hub, where the same files surfaced inside container images. A November 9 GitGuardian analysis counted them all: 31,088 distinct secrets across 23,276 public repos.

Leaks spiked to 12,535 in April 2026. They dropped to 959 by October. The damage was already done. Apiiro’s earlier study, cited by The Hacker News, found 298 more secrets in .claude/settings.json, plus 1,122 real passwords buried in command lines that tools like Gitleaks and TruffleHog missed entirely.

GitHub’s free secret scanning catches known key formats. But generic passwords? Those require AI, and GitHub’s push protection for them remains in public preview. So no alert doesn’t mean clean.

If your repo contains .claude/settings.local.json, search it now: path:.claude/settings.local.json user:YOURNAME on GitHub code search. Then check history: git log --all --full-history --.claude/settings.local.json. Because deleting the file isn’t enough. The secrets live in every commit, every fork, every clone.

GitGuardian says: rotate everything first, new DB passwords, new API keys, new SSH keys, before cleaning up. Then use git-filter-repo to purge the file from history, force-push, add it to .gitignore, .npmignore and .dockerignore, and confirm with git check-ignore -v. Long term? Never paste secrets into shell commands.

Use environment variables. Or patterns like Bash(npm run test:*) instead of full lines. This isn’t just a Claude Code problem. Codex writes rules to ~/.codex/rules/default.rules.

Cursor supports per-project permission files, and tells teams to commit them. Which means whatever’s in there ships with the next push. Anthropic’s patch stops new leaks. It doesn’t undo old ones.

Version 2.1.323 is live. Run claude --version and claude update to get it.

Reported from

How this story was made

Written by the Hitechreports desk from the reporting credited above, with facts attributed to their original publishers. We do not test devices ourselves; anything about performance, battery life or cameras comes from the outlets that did. Prices are as reported at the time of writing. Editorial policy · Report an error

What did you make of it?

Filed by The Computing Desk

Laptops, desktops, processors, graphics cards and the operating systems that run on them.

More from this desk →

Be the first to comment

Join the argument. No password, just your email or a passkey.