AI Agent Credential Leaks: A Business Continuity Checklist
What the Grok Build and Claude Code exposures mean for Singapore companies: why a leaked key stops the business, what buyers will ask, and a checklist.
What happened with Grok Build and Claude Code in November 2026
.claude/settings.local.json. If that command contained a password or API key, the secret sits there in plaintext. Apiiro examined 104,185 public copies of the file on GitHub and found 1,122 holding 1,379 distinct secrets (iTWire). It also reported that popular open-source secret scanners missed a large share of them.
Be precise about the second case: Claude Code did not publish the files. The file is meant to stay on the developer's machine, and a Claude Code team member said Claude Code adds it to .gitignore when it creates the file. Developers committed it to public repositories anyway. To a client whose data leaked, that distinction matters little.Why a leaked AI agent credential is a business continuity problem
What procurement teams will ask about AI agents
.gitignore rules plus a secret scan on every commit.
• How fast can you rotate a key, and what breaks when you do? Show a tested rotation runbook with a stated time.
• How would you know if an agent-built app went public? Show a regular audit of published links.
The scanner results are a warning for anyone who answers "we run a scanner": by Apiiro's account, standard tools missed many of the leaked files. Buyers will start asking how you know your controls work, not just whether you have them.Checklist: what to do this week
.claude/settings.local.json and similar agent config files, and add them to .gitignore.
• Rotate any key that has ever appeared in a config file, a chat with an agent, or a pasted command.Checklist: what to fix this quarter
Frequently asked questions
Did Claude Code leak passwords to GitHub?
Not directly. Choosing "Yes, and don't ask again" saves the approved command in .claude/settings.local.json, which can include a password or key. The file is meant to stay local, but developers committed copies to public GitHub repositories. Apiiro found 1,122 such files holding 1,379 secrets. Keep the file out of version control and rotate any exposed key.
How many Grok Build apps were publicly accessible?
Security firm Claroc found that 35,578 of 37,571 live Grok Build apps, about 95%, opened for anyone without signing in. The default access setting was "Anyone with the link", and app addresses leaked into DNS records. Claroc estimated 650 to 800 held private data. Twenty-four belonged to SpaceXSI and X staff.
Why is a leaked API key a business continuity risk?
Because the fix causes downtime. Once a key leaks you must rotate it, and every system using that key stops until it is updated. Without a list of which apps use which key, recovery can take days. In Singapore, a notifiable breach involving personal data must also be reported to the PDPC within three calendar days.
How should companies store credentials used by AI agents?
Keep credentials in a password manager or secret store and let agents read them from environment variables, so the value never appears in a command, config file or chat log. Keep agent config files out of version control, run more than one secret scanner, and keep a tested runbook for rotating each key.
Related articles
All guides in AI governance, risk and continuityTrain your team on this
We teach teams to use Claude on their own work, and set up a company AI for them. Start with a free 1-hour preview, or see the full package.
Want to Apply This to Your Business?
We're a Singapore AI development and automation agency. Let's discuss how we can help solve your specific challenges.