Skip to main content
Commerce Security logo, "All 12 PCI DSS Requirements in Plain English," "Get it now for free," "Complete Survival Guide" and a button toclick to get it
IncidentSeverity S: serious, 4/5Confirmed: a company, official or court statement

Anthropic's Claude Code 'don't ask again' feature saved developer secrets in plain text, exposed in public GitHub repos

Security firm Apiiro found that Claude Code's 'Yes, and don't ask again' feature saved exact shell commands, including any passwords, API keys and SSH logins typed into them, in plain text to .claude/settings.local.json files that ended up in public GitHub repositories. Apiiro found 1122 such files holding at least one real secret, 1379 distinct secrets in all, rising to 2539 secrets across 1994 repositories when related files were included. Most exposed files belonged to individual developers, but 63 organisations were also affected, and one notified organisation confirmed its key had been live. Anthropic's head of Claude Code, Boris Cherny, said the company is looking into prevention measures but argued the exposed copies had been manually checked in.

What the AI did

When a developer chose the 'Yes, and don't ask again' option, Claude Code saved the exact shell command they had approved, including any passwords, API keys or SSH logins typed into it, in plain text to a .claude/settings.local.json file in the project folder. Some of these files ended up in public GitHub repositories, where anyone could read the secrets.

First reported November 9, 2026 · Added to the register November 14, 2026 · 2 sources

Organisations affected
63
Developer
Anthropic
Model
Claude Code
When it happened
August 2025
First reported
November 9, 2026

What this means for you

Could this affect you?

Yes

If your developers use Claude Code. Developers and 63 organisations had real secrets exposed in public repositories, along with any service whose database passwords, cloud keys, SSH logins or tokens were typed into approved commands.

What to check

  • Rotate every credential the .claude/settings.local.json file has ever held before cleaning it up.
  • Untrack .claude/settings.local.json in your repositories and add it to .gitignore.
  • Reference secrets as environment variables instead of typing them into commands.
  • Search for exposed secrets with more than conventional secret scanners, which missed 215 of these.

Timeline

  1. August 2025Happened
  2. November 9, 2026First reported
  3. November 9, 2026New reporting adds that when Apiiro ran Gitleaks and TruffleHog over the 1,122 files, neither tool raised an alert in 215 cases, that 211 forks of 74 repositories carried the same secrets as the originals, and that a Claude Code issue opened in August 2025 had reported the same problem.[2]
Every fact and its source (9)
  1. Problem first reported by usersAugust 2025
    “Claude Code users have in fact reported the problem in GitHub issues since August 2025.”[1]
  2. Wider tally including related files2539 secrets across 1994 repositories
    “the tally reached 2539 secrets across 1994 repositories”[1]
  3. Live credential confirmedOne notified organisation confirmed its key was live
    “one organisation it notified confirmed its key had been live”[1]
  4. Database credentials exposed379 database passwords and 122 Supabase service-role keys
    “including 379 database passwords and 122 Supabase service-role keys”[1]
  5. Researcher that found the issueApiiro
    “security firm Apiiro has found”[1]
  6. Files with real secrets and distinct secrets1122 files; 1379 distinct secrets
    “Of those, 1122 held at least one real secret -1379 distinct secrets in all.”[1]
  7. Anthropic responseLooking into prevention measures
    “we are looking into what we can do to prevent this”[1]
  8. Spread via forks211 forks of 74 repositories
    “211 forks of 74 repositories carried the same secrets as the originals”[2]
  9. Missed by secret scanners215 cases flagged by neither Gitleaks nor TruffleHog
    “In 215 cases neither tool raised an alert.”[2]

Sources

  1. "Don't ask again" in Anthropic's Claude Code leaks developer secrets
    itnews.com.au · November 9, 2026
  2. 1,379 Passwords on GitHub: Claude Code's 'Don't Ask Again' Approval Files Leaked Live Credentials – The Cherry Creek News
    thecherrycreeknews.com · November 9, 2026

How this record is classified. Severity S (4/5): real harm to one organisation, data exposed, or a containment failure. OECD level: incident, an event in which an AI system led to actual harm. Evidence: Confirmed, meaning a company, official or court statement.

The facts in At a glance and in Every fact and its source are quoted from the sources listed. The summary, What the AI did and What this means for you are written from those sources and checked against them automatically before publication. Records reflect what has been disclosed, not everything that has happened. Incidents are found through news feeds and the GDELT Project.

Promotional banner for the Pentest Readiness checklist download