Claude Code is accidentally exposing secrets all over GitHub

8.2 relevance

Claude Code leaking secrets is a major AI tool security issue, directly actionable for developers.

AI/ML arstechnica.com

Answer the board on AI readiness

Arrive with evidence, not opinion. See how your foundation benchmarks against your peers, get a clear read, and leave with a ranked place to start.

Why It Matters

As a platform engineer using AI coding tools, this highlights a critical security gap in agentic workflows where automated command approval can inadvertently leak infrastructure credentials into public repos, undermining your CI/CD and cloud security posture.

Key Takeaways

Enforce repo-level .gitignore rules for Claude Code settings files and integrate secret scanning (e.g., truffleHog, Gitleaks) into your pre-commit hooks to catch leaked credentials before they reach GitHub.

Claude Code is accidentally exposing secrets all over GitHub

Summary

Apiiro researchers discovered over 100,000 Claude Code settings files on public GitHub, with ~1,100 from 63 organizations containing secrets like database passwords and API tokens. The leak occurs when users approve shell commands with 'Yes, and don’t ask again,' storing the full command—including embedded secrets—in .claude/settings.local.json. While Anthropic adds this file to the global .gitignore, it isn’t repo-level protected, so cloning or reinitializing a repo can expose it; Claude Code may also commit changes without user input.

Author

Kyle Orland — Kyle Orland has been the Senior Gaming Editor at Ars Technica since 2012, covering topics ranging from retro games to new gaming hardware, business and legal developments in the industry, fan communities, gaming mods and hacks, virtual reality...