[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fgNLfmoHhFHDWzg7LgRB1YH9W9IMtXWKB2xr7MiJP5MU":3},{"lesson":4},{"id":5,"slug":6,"article_id":7,"title":8,"body":9,"prevention":10,"framework_refs":11,"framework_notes":19,"status":27,"created_at":28,"published_at":29,"article":30,"tags":34,"podcasts":53,"controls":54},"14d9605b-e762-45f3-857f-6d416903a243","claude-code-ai-tool-leaks-secrets-into-1122-public-github-repos","8132592d-4556-40fc-a77d-d3fda81b3d83","Claude Code AI Tool Leaks Secrets into 1,122 Public GitHub Repos","Anthropic's Claude Code assistant includes a 'Don't Ask Again' feature that persists user-approved commands — including passwords and API keys — into project-level settings files. When developers commit these files to public GitHub repositories without understanding what data is being stored, those secrets become instantly accessible to anyone on the internet. This incident illustrates a dangerous gap between developer convenience features and secure-by-default design: tools that silently write sensitive data to disk can inadvertently automate secret exposure at scale. The core failure is two-fold — the tool's default behavior was not sufficiently protective, and many users lacked awareness that committing project settings files could expose credentials.","**Immediate actions:**\n- Rotate all API keys and passwords found in any Claude Code settings files that have ever been committed to a repository, public or private.\n- Add Claude Code settings files (e.g., `.claude\u002Fsettings.json` or equivalent) to `.gitignore` templates across all projects to prevent future commits.\n- Use a secret-scanning tool (GitHub Secret Scanning, TruffleHog, Gitleaks) to audit all repositories — public and private — for currently exposed credentials.\n\n**Developer tooling & configuration hardening:**\n- Configure pre-commit hooks that block commits containing credential-like patterns before they reach any remote repository.\n- Establish an organisational policy requiring that all AI assistant configuration files storing command history be classified as sensitive and excluded from version control.\n- Evaluate any AI coding tool's data-persistence behaviour during procurement or adoption, ensuring secrets are never written to project directories in plaintext.\n\n**Long-term improvements:**\n- Adopt a secrets-management solution (e.g., HashiCorp Vault, AWS Secrets Manager) so credentials are never typed inline in commands that any tool could capture.\n- Provide mandatory security awareness training covering safe use of AI development assistants, specifically the risks of persistent command histories and settings files.\n- Implement continuous repository scanning in CI\u002FCD pipelines to detect and alert on any secret that slips through pre-commit controls.",[12,13,14,15,16,17,18],"CIS Control 3: Data Protection","CIS Control 14: Security Awareness and Skills Training","NIST SP 800-53 SI-2: Flaw Remediation","NIST CSF 2.0 PR.AA: Identity Management, Authentication, and Access Control","ISO\u002FIEC 27001:2022 A.8.8: Management of technical vulnerabilities","GDPR Article 32","OWASP A06:2021 Vulnerable and Outdated Components",{"GDPR Article 32":20,"CIS Control 3: Data Protection":21,"NIST SP 800-53 SI-2: Flaw Remediation":22,"OWASP A06:2021 Vulnerable and Outdated Components":23,"CIS Control 14: Security Awareness and Skills Training":24,"ISO\u002FIEC 27001:2022 A.8.8: Management of technical vulnerabilities":25,"NIST CSF 2.0 PR.AA: Identity Management, Authentication, and Access Control":26},"If any of the exposed credentials provide access to systems holding personal data, their public disclosure constitutes a failure to implement appropriate technical measures to ensure data security, triggering potential breach-notification obligations.","Sensitive credentials written to project files and committed publicly represent a failure to classify and protect sensitive data at rest; CIS Control 3 requires organisations to identify, classify, and protect data to prevent unauthorised disclosure.","The tool's insecure default behaviour of writing secrets to commitable files represents a software flaw that vendors and adopting organisations should track and remediate through formal flaw-management processes.","Integrating a third-party AI tool without evaluating its data-handling behaviour mirrors the risk of adopting components without security review; OWASP A06 highlights the need to vet all third-party software for security properties before use.","Developers were unaware that Claude Code's convenience feature persisted secrets to disk files; targeted training on AI tool risks and version-control hygiene would have prevented the accidental commits.","The insecure default configuration of Claude Code is a known technical vulnerability that organisations adopting the tool should assess, track, and mitigate as part of their vulnerability management programme.","Exposed API keys and passwords directly undermine credential integrity; this function requires that credentials be protected throughout their lifecycle, including during storage by developer tooling.","published","2026-11-07T08:20:27.580912+00:00","2026-11-07T08:20:27.56+00:00",{"id":7,"url":31,"slug":32,"title":33},"https:\u002F\u002Fthehackernews.com\u002F2026\u002F11\u002Fclaude-codes-dont-ask-again-file.html","claude-code-s-don-t-ask-again-file-exposes-passwords-and-keys-in-1-122-public-co-9989e9","Claude Code's “Don't Ask Again” File Exposes Passwords and Keys in 1,122 Public Copies on GitHub",[35,41,47],{"id":36,"name":37,"slug":38,"description":39,"color":40},"7261eb8f-acd4-4d93-a489-7fdd652ec0ea","Security Awareness","security-awareness","Phishing, social engineering, human error","#22c55e",{"id":42,"name":43,"slug":44,"description":45,"color":46},"859cf0ad-a7e9-42bb-a75d-bac6511fa5d5","Configuration Management","configuration-management","Misconfigs, default credentials, exposed services","#eab308",{"id":48,"name":49,"slug":50,"description":51,"color":52},"c8b843a5-d5a7-41d1-8d3b-cabded09d2ef","Data Protection","data-protection","Unencrypted data, missing DLP, poor classification","#3b82f6",[],[55,59,63],{"slug":56,"name":57,"problem":58},"secrets-management","Secrets management","API keys, tokens and passwords stop leaking from code, chat and configuration files.",{"slug":60,"name":61,"problem":62},"data-loss-prevention","Data loss prevention (DLP)","Sensitive data cannot quietly leave by email, upload, USB stick or AI tool.",{"slug":64,"name":65,"problem":66},"security-awareness-training","Security awareness training and phishing simulation","People recognise and report attacks instead of falling for them."]