International
The Morning Dev

Only the news worth knowing

‹
 
A63/100

Breach · high

Claude Code accidentally exposes secrets on GitHub

Tier A · Patch today – Before you go home

Who’s exposed: Developers whose Claude Code settings files were committed to public GitHub repos

Tier A because: Core infrastructure or popular tool AND secrets exposed

Reach

Attack

Damage

Fix

Popular tool · Secrets exposed

What to do

  1. Check public GitHub repositories for committed Claude Code settings files and remove any secrets they contain.
  2. Rotate any credentials that may have been exposed, such as database passwords and API keys.

The Brief

  • Apiiro researchers found thousands of secrets, including database passwords and API keys, exposed on public GitHub repositories.
  • The exposure stems from a partial oversight in how Claude Code handles its settings files.
  • Ars Technica reported the findings on 2026-11-09.

Why it matters

Developers who commit Claude Code settings files to public repositories may have credentials such as database passwords and API keys publicly visible, so those repositories should be checked.

The checklist behind the tier

Checklist · 3 of 10 yes
YesHits tech teamsJudgment: Claude Code is a developer tool used by engineering teams.
NoCore infrastructureJudgment: an AI coding assistant is not foundational software like OpenSSH or the Linux kernel.
YesPopular toolJudgment: Claude Code is a mainstream AI coding tool used by many developer teams.
NoExploited in the wildArs Technica: Apiiro researchers found exposed secrets; no observed attacks using them are reported.
NoPublic exploitArs Technica: describes a settings-file oversight found by researchers; no exploit code or PoC is mentioned.
NoRemote, no loginArs Technica: secrets are exposed on public GitHub; no attacker access method is described.
NoFull takeoverArs Technica: leaked database passwords and API keys are exposed; no code execution or takeover is reported.
YesSecrets exposedArs Technica: Apiiro found thousands of secrets, including database passwords and API keys, exposed on GitHub.
NoSupply chainArs Technica: describes a settings-file handling oversight; no malicious code shipped through a trusted channel.
NoNo fix yetArs Technica excerpt: no mention of a vendor fix or patch status.

Timeline

  1. Ars Technica reports Apiiro's finding of thousands of exposed secrets on public GitHub

  2. AI - Ars Technica

    Claude Code is accidentally exposing secrets all over GitHub

Source

Claude Code is accidentally exposing secrets all over GitHub ↗ AI - Ars Technica · 2h ago

First seen · 1 source · Full story page · How tiers are decided