SecurityOnlineDo Son
Apiiro finds Claude Code secrets exposed in 1,994 repositories
Part of the Apiiro story · since 7 Nov
- Sat 7 Nov, 08:30 UTC. The Hacker News, first report. Apiiro finds secrets exposed in 1,122 public Claude Code files.
- Sun 8 Nov, 16:00 UTC. SecurityOnline, its first report on the story. Apiiro finds Claude Code secrets exposed in 1,994 repositories. This article, 2nd of 4.
- Mon 9 Nov, 03:31 UTC. SANS ISC, its first report on the story. SANS honeypots detect exploitation attempts targeting sshole flaw.
- Mon 9 Nov, 18:01 UTC. Ars Technica, its first report on the story. Apiiro finds Claude Code settings exposed secrets on GitHub.
Apiiro researchers Shmulik Cohen and Matan Giladi found that Claude Code leaked secrets across 1,994 public GitHub repositories after developers opted “Yes, and don’t ask again” during coding sessions. The tool writes the exact shell command and any embedded password into a local configuration file named settings.local.json, which is then added to the project and can be committed to public repositories despite a gitignore rule.
In total, the researchers identified 2,539 real secrets across 1,994 repositories, with 1,379 distinct secrets on default branches across 1,122 active files. Exposed credentials include 398 service API tokens, 379 database passwords, and 149 AI model API keys, along with 122 Supabase service-role keys, 110 Google API keys, 103 Supabase account tokens and 43 SSH server logins.
Among the most severe findings were a database vendor’s admin-level cloud key, a Square production token, and an owner password for a medical-records database. The analysis involved examining Git history, shared settings files and agent transcripts; researchers did not test credentials or contact hosts, to respect legal boundaries, instead defining “real secrets” by provider format or password with a public host.
The exposure was measured between 1 and 3 November 2026, with notifications issued on 2–3 November. Affected organisations number 63, including startups, payments firms, universities and software vendors; beyond GitHub, exposure was seen on Hugging Face Spaces and GitLab. The report notes that some credential scanners failed to detect these leaks, with tools like gitleaks and TruffleHog missing 215 of the 1,122 exposed files.
Apiiro has told the 63 organisations to revoke compromised keys, and Anthropic stated that Claude’s underlying behaviour remains unchanged through models up to Opus 5.5. The authors emphasise remediations such as searching for settings.local.json and turning credentials into environment variables, alongside updating pre-commit scanners to catch inline passwords.
How the story developed
4 articles from 4 outlets since 7 Nov. Still developing; the latest report was 22 hours ago. This was the 2nd report, 1 day after the first.
- Sat 7 Nov, 08:30 UTC. The Hacker News, first report. Apiiro finds secrets exposed in 1,122 public Claude Code files.
- Sun 8 Nov, 16:00 UTC. SecurityOnline, its first report on the story. Apiiro finds Claude Code secrets exposed in 1,994 repositories. This article, 2nd of 4.
- Mon 9 Nov, 03:31 UTC. SANS ISC, its first report on the story. SANS honeypots detect exploitation attempts targeting sshole flaw.
- Mon 9 Nov, 18:01 UTC. Ars Technica, its first report on the story. Apiiro finds Claude Code settings exposed secrets on GitHub.
- No CVE
- Larger: an outlet’s first report
- Coverage over time
Show all 4 articles as a listHide the list
- Sat 7 NovDay 01
- Apiiro finds secrets exposed in 1,122 public Claude Code files08:30 · The Hacker News · First report
- Sun 8 NovDay 11
- Apiiro finds Claude Code secrets exposed in 1,994 repositories16:00 · SecurityOnline · This article, 2nd of 4
- Mon 9 NovDay 22
- Apiiro finds Claude Code settings exposed secrets on GitHub18:01 · Ars Technica