Story
Trending

Report finds exposed credentials in public Claude Code settings files

AI · First reported 7 Nov, 06:44 · Updated 08:04

Image: Wikimedia Commons · Rekia1991 · CC BY-SA 4.0

Apiiro reported that 1,122 public copies of Claude Code settings files contained at least one secret, with some credentials also present in repository history and forks. The report says users should rotate affected credentials before removing exposed files.

  • When users approve an exact command and choose not to be asked again, Claude Code can save that command in a project settings file, including any password or token typed into it.
  • Apiiro found 1,122 copies containing secrets among 104,185 copies of the file on public GitHub; the researchers said they did not test whether all the credentials still worked.
  • The researchers recommend rotating credentials before cleanup, checking repository history, and keeping secrets out of commands saved in allow rules.
Summary written by Lux AI from 2 articles

Key facts

Public copies examined
104,185 copies across 103,617 repositories.
Copies with at least one secret
1,122.
Different secrets in those copies
1,379.
Secrets including older versions, shared files and saved agent chat logs
2,539 across 1,994 repositories.
Scanner results
Gitleaks flagged 564 of the 1,122 files and TruffleHog flagged 643; neither flagged 215.

Source spectrum

Far left
Left
Lean left
Centre
Lean right
Right
Far right

Unrated

Left 0 · Centre 1 · Right 0 of 1 rated sources · +1 unrated

Background

All coverage

Coverage over time

0106101418220206
LeftCentreRight

Articles per hour since first reported, by side.

Ownership

  • Unknown 50% (1)
  • Corporation 50% (1)

Share of the 2 sources by owner type.