543,699 Exposed GitHub Credentials Remain Active and Enter AI Training Data
Breach & Incident Intelligence · 10 sources · Updated 1mo ago · First seen Jul 27, 2026

Truffle Security found that 543,699 unique credentials exposed in public GitHub code were still valid when tested on July 27–28, 2026. Its analysis linked those live secrets to 1,103,438 exposures across files and forks in The Stack v3, a 15.9 TB code dataset assembled from about 224 million public repositories. The credentials included API keys, access tokens, database connection strings, and cloud service-account credentials; the median duration of public exposure was 784 days, and one active AWS key had been committed in 2009.
GitHub push protection reduced exposure density by 53% for supported secret types, but it does not remediate historical commits and has incomplete coverage: 51.8% of active credentials used formats not blocked by default protection, while 36.8% were committed after push protection became the default for free users. Google Cloud service-account credentials, MongoDB connection strings, and Google API keys were among the largest groups of usable secrets. Because revocation is not mandatory after GitHub reports findings to providers, organizations should scan full Git histories, immediately revoke or rotate exposed credentials, investigate potential abuse, adopt short-lived secrets, and automate alert-to-revocation workflows; the exposures may also persist in downstream AI-training datasets after removal from source repositories.


