Hardcoded MCP credentials found in public GitHub files
Hush Security found 12% of 82,000 public GitHub MCP config files contained hardcoded API keys, bearer tokens, and database passwords.
Hush Security's 'The State of MCP Configuration: The Identity Security Gaps' report analyzed roughly 82,000 MCP configuration files in public GitHub repositories, finding that 12% of credential slots contained hardcoded credential literals. Researchers used provider-specific token patterns and Shannon entropy to identify likely secrets, predominantly vendor API keys, bearer tokens, and database passwords. Of 7,681 credential-bearing configurations whose history was examined, 243 had secrets removed from the current file but still recoverable from earlier Git commits. Many exposed credentials were high-impact: 53% of classified credentials granted organization-, account-, workspace-, or database-wide access, and 80% with a defined expiration policy did not expire by default.
- 12% of ~82,000 scanned MCP config files contained hardcoded credential literals
- 243 of 7,681 configs had secrets lingering in Git history after deletion
- 24% of hardcoded secrets were broad-scope and non-expiring by design
- 55% of secrets had no vendor-recognizable token format, hindering detection
- MCP agents act as non-human identities needing ownership and lifecycle tracking
- Vendors
- Hush SecurityGitHub
- Products
- Model Context Protocol
- Organizations
- Hush SecurityGitHub
From the original article
3 min read at helpnetsecurity.com
Hardcoded API keys, access tokens and other credentials used by AI coding tools have been found in publicly accessible MCP configuration files on GitHub, according to research from Hush Security’s The State of MCP Configuration: The Identity Security Gaps report.
By Anamarija Pogorelec · helpnetsecurity.com
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.