Skip to content
ViqusViqus
Navigate
Company
Blog
About Us
Contact
System Status
Enter Viqus Hub

Claude Code Leaks Thousands of Secrets via GitHub Settings Files

Claude Code Security Vulnerability API Tokens GitHub LLM Security Secrets Management
November 09, 2026
Source: Ars Technica AI

This summary and analysis were generated by AI from the original article at Ars Technica AI and may contain errors (how Viqus works). Read the source for full details.

Viqus Verdict Logo Viqus Verdict Logo 7
Configuration Leakage Risk
Media Hype 5/10
Real Impact 7/10

Article Summary

Security researchers from Apiiro discovered a significant vulnerability where Claude Code can leak sensitive credentials, including database passwords and API tokens, into public GitHub repositories. The issue arises because the local settings file, which stores user approvals for automated shell commands, sometimes embeds the raw command—and any secrets within it—into a file that is not always correctly ignored by Git. While Anthropic's documentation suggests this file is usually ignored, the researchers found over 100,000 instances of this file being uploaded publicly, exposing credentials from dozens of organizations.

Key Points

  • Claude Code's handling of user approvals for shell commands writes potentially sensitive data into the local settings file.
  • The settings file can be accidentally committed to public GitHub repositories, exposing credentials like API tokens and passwords.
  • Even after removal, leaked secrets can persist in forks of the original project, requiring user vigilance.

Why It Matters

This incident highlights a critical gap in the security tooling surrounding advanced AI assistants. While the core LLM capability might be sound, the integration points—how the tool interacts with the user's local environment and version control systems—introduce significant, easily exploitable risk. Companies relying on AI coding assistants must implement stricter, automated pre-commit hooks specifically designed to scan for secrets in configuration files generated by AI tools, treating AI-generated settings files with the same scrutiny as any manually written code.


You might also be interested in