1,122 Leaked Settings Files: Have Claude Code Check Your Repo for Saved Passwords Before Someone Else Does
- Level Intermediate
- Setup1–3 hrs (estimated)
- Evidence Some evidence
- CostNot stated in source
- No-codeNo
What did they do with Claude Code?
Researchers at Apiiro found more than a thousand public GitHub repos with a Claude Code .claude/settings.local.json that held secrets. Clicking 'Yes, and don't ask again' can save the exact approved command, password or key included, and the file sometimes gets committed. A simple agent task: scan your repos and git history for that file, rotate anything exposed, then untrack it.
How it went
Ars Technica report (Nov 2026) on Apiiro research: public GitHub copies of Claude Code's .claude/settings.local.json with secrets, saved from 'Yes, and don't ask again' approvals. X posts on Nov 11 cited 1,122 files and 1,379 distinct credentials. Security-hygiene task; no personal result claimed. Rotate keys first; deleting the file doesn't remove it from git history or from anyone who already cloned it
Worth knowing
- Ars Technica report (Nov 2026) on Apiiro research: public GitHub copies of Claude Code's .claude/settings.local.json with secrets, saved from 'Yes, and don't ask again' approvals. X posts on Nov 11 cited 1,122 files and 1,379 distinct credentials. Security-hygiene task; no personal result claimed.
- Rotate keys first; deleting the file doesn't remove it from git history or from anyone who already cloned it.
Prompt
Cleaned version rewritten from the source — not a direct quote.
Check every repo in [folder] for .claude/settings.local.json or similar agent settings files, including in git history (git log --all -- .claude/settings.local.json). List any API keys, tokens or passwords found, without printing them in full. Tell me which ones to rotate first, then add the file to .gitignore and remove it from tracking. Don't rewrite history without asking me.
Recommended
Try it in Grok Bot
Grok Bot can run the same repo check on its own computer, or hand it to Claude Code.
- Copy the prompt (button below).
- Open Grok Bot chat and paste it. Replace any [bracketed] placeholders.
- Connect the listed tools (GitHub) as connectors when Grok Bot asks.
- If the task repeats, ask: "Make this a daily routine."
Alternatives: the same prompt works in Claude Code, Claude, ChatGPT Agent, OpenClaw.
Set it up
Tools: GitHub · Stack: Claude Code
- Read the original source for full context.
- Connect the tools your agent needs.
- Paste the prompt and replace [bracketed] placeholders.
- Run once manually and check the output before scheduling it.
Generic suggested steps, not from the source.
Evidence
Ars Technica report (Nov 2026) on Apiiro research: public GitHub copies of Claude Code's .claude/settings.local.json with secrets, saved from 'Yes, and don't ask again' approvals. X posts on Nov 11 cited 1,122 files and 1,379 distinct credentials. Security-hygiene task; no personal result claimed. Rotate keys first; deleting the file doesn't remove it from git history or from anyone who already cloned it (as of 2026-11-10)
Source: Web · 2026-11-10 · Verified by us: not yet · Report broken or outdated