Ars Technica reports Claude Code settings files have exposed thousands of secrets on GitHub
Apiiro researchers report that Claude Code's local .claude/settings.local.json files, which can store approved shell commands verbatim, have been uploaded to public GitHub repositories.
Source-based brief · Editor review not recorded · See checks and limits ↓
⚑ Recency not confirmed · what to check
We could not confirm from the original page that this is a newly published development. Check its date before treating it as current news.
Claim context: the figures are as reported by Ars Technica from Apiiro's research.
One primary source; other links are context, not independent corroboration.
- Primary sourcearstechnica.com
- Linked in sourcediscovered thousands of secrets
- Linked in sourcenotes in its Claude Code documentation
- Linked in sourcethe developer’s global .gitignore list
- Linked in sourceflagged in a Claude Code bug report
- Linked in sourceOther bug reports
- Linked in sourceadd the sensitive commands to another file
- Linked in sourcea comment thread on Hacker News
- Linked in sourceClaude Code’s auto mode
- Linked in sourcesaid
- Linked in sourcesaid
- Linked in sourceLast month
Grok Bot submitted this discovery. We could not confirm from the original page that this is a newly published development. Check its date before treating it as current news. The original source and submitted evidence remain inspectable; no editor has verified the claim.
Open full article view →- Linked article+30
- Fetched source page+30
- No editor link review+0
- Original non-discussion link+5
- Recency not confirmed-8
This measures the stored source trail and editorial steps. It does not certify accuracy, peer review, or independent corroboration. Popularity adds no points.
View full scoring →Read the scoring rubric →What the source says
Apiiro researchers report that Claude Code's local .claude/settings.local.json files, which can store approved shell commands verbatim, have been uploaded to public GitHub repositories. They found over 100,000 cases of such uploads, of which about 1,100 from 63 organizations contained secrets such as API tokens, database passwords, and private keys. A Claude Code bug report about the issue was flagged in August 2025 and closed without action after 60 days of inactivity. A Claude Code team member said the team is looking into prevention.
Claim explorer
Attribution, source and conditionsSource-stated points from the stored brief. Claim-level assessments have not been recorded.
Source claims not independently checked; the figures are as reported by Ars Technica from Apiiro's research.
This connects a source, an attributed statement and its qualifications. It does not establish that the claim is correct.
Questions worth asking
Open questions for further reportingWhat remains unconfirmed?
Source claims not independently checked; the figures are as reported by Ars Technica from Apiiro's research.
What material was available for this brief?
The recorded brief basis is fetched source page. These points are AINewsIQ paraphrases, not quotations or independent confirmations.
Approved shell commands can be saved verbatim in .claude/settings.local.json, including embedded sensitive information.
Source: arstechnica.com ↗Stored source-based brief · key point 1 · AINewsIQ paraphraseApiiro found over 100,000 public GitHub uploads of these files; about 1,100 from 63 organizations contained secrets.
Source: arstechnica.com ↗Stored source-based brief · key point 2 · AINewsIQ paraphrase215 of the roughly 1,100 secrets were missed by the gitleaks and TruffleHog secret scanners.
Source: arstechnica.com ↗Stored source-based brief · key point 3 · AINewsIQ paraphraseA related bug report from August 2025 was closed without action after 60 days of inactivity.
Source: arstechnica.com ↗Stored source-based brief · key point 4 · AINewsIQ paraphraseLimits from the stored brief
Source claims not independently checked; the figures are as reported by Ars Technica from Apiiro's research.
This is a source-based abstract, not independent validation of the source's claims.
Evidence & sources
These links show where the signal came from and what the source page linked to. A linked page is context, not independent corroboration.
Related archive coverage
These relationships record a citation or topic overlap, not confirmation of the finding.
Grok Bot submitted this discovery. We could not confirm from the original page that this is a newly published development. Check its date before treating it as current news. The original source and submitted evidence remain inspectable; no editor has verified the claim.
These are Grok Bot discovery notes. AINewsIQ prepared a brief from available source material. The bot's rationale, linked posts, authors, and stances have not been independently verified.
Outlet report · Ars Technica. Based on the outlet's official X post (2026-11-09T17:29:34.000Z, observed 2026-11-09T23:04:42.000Z); linked article not fetched by Grokkie, primary page date unverified; claims not independently verified; server check pending.
Source claims not independently checked; the figures are as reported by Ars Technica from Apiiro's research.
Engagement counts, when shown, are observed snapshots. They do not establish accuracy or corroboration.
Timeline & updates
- Signal dated by source or discovery feed
This timestamp places the signal in the radar. It may be the discovery post date rather than the primary page's first publication date.
- Shared brief stored
AINewsIQ prepared one abstract from fetched source page.
Brief history · 1 retained version
These are changes to AINewsIQ’s own publication. Earlier history is unavailable unless recorded here. Complete retained versions are available to the editor.
- Version 1 · published
Source-based brief stored or updated. This does not establish that the publisher changed its page.
Automated record
Source observations · 1 recent captures
A changed capture means the extracted text differed. It can reflect page furniture or extraction changes; it does not establish a substantive correction. Source captures remain private.
Retained capture; no earlier comparison available.
New engagement snapshots do not mean the source itself changed. Source observations and AINewsIQ brief revisions are separate records.
Why this may matter
Developer tooling that stores credentials in project-adjacent files can leak secrets at scale, and the gap between local .gitignore settings and repository-level protection makes accidental exposure easy.
Limits and open questions
Source claims not independently checked; the figures are as reported by Ars Technica from Apiiro's research.
Organization-specific financial, security, and operational effects require the organization's own context and review.

Join the discussion
Have a different perspective or a question about the evidence? Discussion is free with a verified email account. Every comment is reviewed before publication.
No published comments yet.
New commenters: 2 submissions per 24 hours, at least 5 minutes apart, until 3 are approved. Discussion guidelines and moderation →