Claude Code Saved Passwords in 1,122 Public GitHub Files. Ask Your Web Developer About Yours.
Security firm Apiiro published research this week, and The Hacker News covered it Friday, about one small button in Claude Code. That's Anthropic's coding tool, and a lot of freelancers and web developers use it now. When it asks permission to run a command, one of the choices is "Yes, and don't ask again." Pick that, and Claude Code saves the command in a file called settings.local.json inside the project folder. If the command had a password in it, the password gets saved too, in plain text.
Apiiro went looking on GitHub and found 104,185 public copies of that file. About 1,122 of them held at least one secret, 1,379 in all. Among them were 379 database passwords and 23 Amazon cloud keys. Apiiro didn't test whether the passwords still work, though one company it contacted said its key was live. The Hacker News says the researchers' reports to Anthropic went unanswered. I couldn't open Apiiro's original write-up, so every number here comes from The Hacker News coverage.
Why a Toledo business owner should care
You probably don't use Claude Code. Your web developer might, or the marketing freelancer, or the nephew who built your booking page. Your website's code almost always lives on GitHub, and if that project got published with one of these files in it, anything typed into those commands is sitting there for anybody to read. That could be the password to your website's database, or a login to the server your site runs on.
Half the affected files had been up for at least 217 days. Nothing broke, so nobody noticed.
What I'd do this week
Send your developer a short email with two questions. Do you use Claude Code or any other AI coding tool on my project, and is a .claude folder in my GitHub repository? If they're not sure, ask them to search the repo for settings.local.json. While you're at it, find out whose GitHub account actually holds your site's code. Sometimes that turns out to be a former contractor, and you want to know before something goes wrong.
If they do find a password in there, the order matters. Change the password first, then delete the file. Old copies stay in the project's history, so deleting alone doesn't fix anything. Apiiro's advice, as reported, is also to keep secrets out of commands in the first place and use a variable name instead, so the saved rule holds the name and not the password.
Plenty of good developers use these tools and they save real time, so I wouldn't tell anybody to stop. This is a ten minute conversation, and it beats hearing about it from a stranger who found your database login on the internet.
I run AI workshops and one-on-one AI consultations for companies around Toledo, Northwest Ohio, and Southeast Michigan. If you want help figuring out what the people building your website are allowed to do with AI tools, email me and we'll sort it out together.
Email Jayson