Unverified50% confidenceFactExact time
If a local configuration file containing sensitive commands is accidentally committed and pushed to a public GitHub repository, credentials will be exposed.
1
Sources
50%
Confidence
Long-term
Relevance
11/14/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedThe GitHub Releases page displays incompletely when scripts are blocked or the network is restricted, so key information is best cross-confirmed from commit records and the CHANGELOG.73% similarUnverifiedA compromised GitHub account may be used to inject malicious commits into open-source projects, constituting a software supply chain attack.73% similarUnverifiedThe leak path is: after the developer checks "Don't Ask Again", Claude Code gains persistent access to a specific directory or file type; subsequently, files containing passwords are brought under version control and pushed to public GitHub repositories, causing the sensitive information to be fully exposed.72% similarUnverifiedIt is recommended to add known sensitive filenames (such as settings.local.json) to git-secrets or gitleaks scanning rules to establish default protection.71% similarUnverifiedClaude Code was reported to have accidentally exposed sensitive information such as passwords and API keys on GitHub.71% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1170040API
curl https://kongchang.com/api/v1/knowledge/claims/1170040MCP
get_claim(id=1170040)