Study finds 543,699 still-valid credentials exposed on GitHub

The findings describe access information left public for years, but do not establish whether anyone misused it.

The findings describe access information left public for years, but do not establish whether anyone misused it.
A Truffle Security study found 543,699 unique credentials exposed in public GitHub repositories that were still valid as of July 2026, The Hacker News reported on October 1. Credentials are information used to prove identity or gain access to a system. The finding concerns working access information, not merely obsolete data left online.
GitHub repositories store code and related files; public repositories are open for others to view. The Hacker News quoted Truffle Security as saying the median credential had spent 784 days in a public default branch—the repository’s main line of development. That means half had been exposed for at least that long. The oldest credential was committed in 2009 and still worked, according to the same account.
The Hacker News also quoted Truffle Security as saying that just under 200,000 of the credentials were pushed—uploaded to GitHub—after the platform enabled push protection by default. Push protection is a security measure intended to prevent credentials from being uploaded. The timing does not establish whether or how that protection applied to each exposure, or why the uploads occurred.
It is not clear how many repositories the study covered, which types of credentials it counted or how Truffle Security checked their validity. The count therefore does not establish a leakage rate across GitHub. Whether anyone used the exposed credentials without permission also remains unknown: public exposure and continued validity are not proof of a compromise.

Truffle Security’s findings highlight two limits of GitHub’s upload checks: they do not invalidate old leaks or block every kind of credential.
3 min