Truffle Security Finds 543,699 Working Credentials in Public GitHub Repositories
Security / news
Truffle Security Finds 543,699 Working Credentials in Public GitHub Repositories
The median leaked secret had sat in a public repository for 784 days, and GitHub push protection covers only part of what leaks.

Truffle Security found 543,699 unique credentials that still worked in public GitHub repositories, with a median exposure of 784 days, according to a report it published. The company validated each one against its issuing service on July 27 and 28, 2026.
These are live credentials in public repositories: keys that authenticate, not keys anyone is known to have abused. The report counts access that exists, not access that was taken. Truffle scanned 224 million public repositories, and the figures are its own; The Terminal could not independently verify them.
How old the leaked credentials are
The Hacker News, in a bulletin covering the study, quoted Truffle's line that "the median one had been sitting in a public default branch for 784 days. The oldest was committed in 2009 and still works."
Truffle splits the 543,699 by when the credential was committed, against GitHub's own protection milestones. The largest group predates GitHub's free secret alerts.
- Before free alerts (Feb. 2023)246K credentials
- Alerts available, push protection optional (Feb. 2023 to Feb. 2024)98K credentials
- Push protection on by default (Feb. 2024 on)200K credentials
Source: Truffle Security, validated July 27 and 28, 2026
The last bar is the awkward one. Nearly 200,000 working credentials, 36.8 percent of the total, were pushed after GitHub made push protection the default in February 2024.

Why push protection leaves half of them through
Truffle says push protection cut new exposure by about 53 percent for the patterns it recognizes. It only blocks vendor-prefixed tokens, the kind whose format identifies the issuer. Truffle puts the credentials outside that net at 51.8 percent of every live one, mostly database connection strings, Google API keys and private keys.
A string like postgres://user:password@host/db has no prefix to match, which is why it passes.
Which credentials die and which survive
Truffle's survival rates split by whether the provider has automated revocation. npm tokens show 0.001 percent survival: one live token out of 101,886 committed. GitHub's own tokens survive at 0.36 percent.
| Credential type | Share still live |
|---|---|
| npm tokens | 0.001% |
| GitHub tokens | 0.36% |
| MySQL connection strings | 75% |
| PostgreSQL connection strings | 88% |
The gap is the finding: types with automated revocation almost never show up live, and database strings mostly do. Truffle's advice is to "treat a committed credential as burned the moment it lands" and rotate it, instead of relying on scanning or blocking.
What to check first
On Truffle's numbers, the practical order is to rotate database connection strings and Google API keys first, since those are the types push protection does not block and the PostgreSQL and MySQL strings are the ones most often still live.
Credentials in a developer's reach are also the target in attacks we have covered, such as a fake NDA branch that carried a git post-checkout hook and the agent-sandbox work around NVIDIA's OpenShell. Truffle's July snapshot is the figure to compare against if it publishes a follow-up.
Sources
More in Security
- 01Ruby2Shell (CVE-2026-132825): Ruby Is Fixed, but GitLab, GitHub Enterprise and Chatwoot Are Listed Without a PatchA one-byte heap overflow in Ruby's case conversion carries a 7.4 local score, while the researchers say stock Rails is remotely reachable and will publish a proof of concept Nov. 25.
- 02NPCI Wants Overlay Permissions Restricted on Sideloaded Apps; Google's 2024 India Block List Omits ThemThe reported ask covers accessibility, device admin and display-over-apps. The pilot Google announced on Oct. 3, 2024 named four other permissions.
- 03CVE-2026-99312: A KVM Nested-AMD Bug Scores 8.8, With Fixes Listed for Three Kernel BranchesThe Linux CNA's scoring notes describe a freed page-table root that a guest can aim at; the commit message describes only a stale MMU context.
- 04CISA's Nov. 18 KEV Additions Include Apache Axis 1.x, Which Has No Fix, With a Nov. 21 DeadlineThree of four new entries carry a three-day federal deadline; LiteLLM's advisory names two different patched versions.