Trump administration announces funding for PTSD research on ibogaineWIRED investigation examines Jensen Huang's comments on defining women's power in techWalmart launches early Black Friday promotions on select giftsMint Mobile offers $500 discount on select new phones for new customers signing up for a yearRussia and Iran criticize U.S. Caspian task force amid reports of joint sanction evasion effortsNewly elected US lawmakers pose for traditional group photo at Capitol ahead of 120th Congress openingUS existing home sales drop to lowest monthly level in yearsPro-Palestine philanthropist faces US extradition hearing in SpainLewisham Islamic Centre criticizes charity watchdog over warning on Palestine commentsSenegalese wrestlers succeed in beach wrestling at Dakar Youth OlympicsUS nonprofits file lawsuit seeking pause on advanced AI model trainingDemocrats convene in Denver to discuss party direction after midterm victoriesUS releases report on $12bn from Venezuelan oil, mineral resourcesPope Leo XIV urges Catholic Church to address clergy sexual abuseShooting near White House results in death, suspect later found dead
Back to event

Claude Code is accidentally exposing secrets all over GitHub

By Kyle Orland · Nov 9, 2026, 11:24 AM CST

Read full article at Ars Technica
Claude Code is leaking sensitive information on public GitHub instances thanks to a partial oversight in the way its settings files are handled. That's the finding of AI security researchers at Apiiro, who discovered thousands of secrets , including database passwords, API tokens, and root logins, amid Claude Code settings files embedded in GitHub repositories. The leak stems from the way Claude C

Excerpt shown under fair-use limits. Full text remains with the original publisher.

People in this coverage

Explore their history and attributable record. Being mentioned does not imply endorsement.

Layer 1 · Claims & fact checks

AI analysis

Layer 2 · Biblical perspective

Biblical interpretation
UNHOLY / UNRIGHTEOUS
Read the biblical analysis

Layer 3 · Reporting analysis

AI analysis

SensationalismThe headline and opening sentence use strong language (“leaking”, “exposing secrets”) to create alarm without presenting corroborating data.

Appeal to AuthorityThe article invokes Apiiro as an authority but does not provide details of their analysis or link to a report.

Mitigation MinimizationThe author downplays the potential risk, suggesting the issue is minor under certain conditions.

Context

AI analysis

Missing context

The article does not provide details about how many repositories were actually affected, the proportion of repositories where the .claude/settings.local.json file was unintentionally committed, or any response from Anthropic or affected developers. It also lacks information about the methodology used by Apiiro to identify the alleged secrets.

Important context

Claude Code's settings file is designed to be ignored by Git via a global .gitignore entry, which would normally prevent it from being pushed to public repositories. The security impact depends on whether that ignore rule was overridden or omitted.

Opinion vs. reporting

AI analysis

The piece mixes reporting of a claimed security finding with opinionated language (e.g., "This isn't really a significant security issue if the settings file stays on the user's local machine"). It presents the Apiiro claim without independent verification, leaning toward a sensational framing.