<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/over-543-000-valid-credentials-exposed-in-public-github-repositories-fblhmhuem" -->

---
title: Over 543,000 valid credentials exposed in public GitHub...
description: A Truffle Security scan of 224 million GitHub repositories and over 58 billion files found 543,699 unique valid credentials exposed publicly as of July, with a...
canonical: https://daily.dev/posts/over-543-000-valid-credentials-exposed-in-public-github-repositories-fblhmhuem
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Over 543,000 valid credentials exposed in public GitHub repositories | daily.dev
og:description: A Truffle Security scan of 224 million GitHub repositories and over 58 billion files found 543,699 unique valid credentials exposed publicly as of July, with a...
og:url: https://daily.dev/posts/over-543-000-valid-credentials-exposed-in-public-github-repositories-fblhmhuem
og:image: https://api.daily.dev/og/posts/fBLHMhUEM.png
og:image:alt: Over 543,000 valid credentials exposed in public GitHub repositories
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Over 543,000 valid credentials exposed in public GitHub repositories

**[BleepingComputer](https://daily.dev/sources/bleepingcomputer)** · 3 min read · 1 upvotes · 0 comments

## Summary

A Truffle Security scan of 224 million GitHub repositories and over 58 billion files found 543,699 unique valid credentials exposed publicly as of July, with a median exposure time of 784 days. GitHub's Push Protection, enabled by default since February 2024, cut exposure rates by 53% within the categories it covers, but 51.8% of live credentials fall into types it doesn't block, such as database connection strings and Google API keys. Revocation rates vary wildly by service: nearly all leaked npm tokens were dead, while over half of exposed Google Cloud service account credentials were still active. The findings more than double a prior scan of Hugging Face, which found 221,303 working credentials.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.bleepingcomputer.com/news/security/over-543-000-valid-credentials-exposed-in-public-github-repositories>

## Questions this post answers

### How many valid credentials were found exposed in public GitHub repositories in a recent large-scale scan?

A scan of 224 million public GitHub repositories and over 58 billion files by Truffle Security found 543,699 unique valid credentials still working in July, appearing across more than 1.1 million files and repositories including forks. The median exposure time was 784 days, and about 10% of the credentials were older than 6.3 years, with the oldest dating to 2009.

_Anyone auditing repo hygiene can track findings like this credential exposure research on daily.dev._

### Does GitHub's Push Protection stop all types of leaked credentials?

No, Push Protection blocks only certain secret patterns by default, and 51.8% of the valid credentials found in a 2025 scan fell into categories it does not cover, such as database connection strings and Google API keys. Within the categories it does cover, exposure rates dropped 53% after GitHub enabled the feature by default for all users in February 2024.

_Teams configuring secret scanning coverage can follow ongoing analysis like this on daily.dev._

### Which types of leaked cloud credentials are most likely to still be active after being exposed on GitHub?

Google Cloud service account credentials had a high live rate: of 126,963 exposed, 69,041 were still valid and working. By contrast, npm tokens were almost always revoked, with only 1 of 101,886 committed tokens still functional, showing that revocation practices vary sharply by service and credential type.

_Developers deciding which secrets to prioritize rotating can keep up with findings like this on daily.dev._

## Similar posts on daily.dev

- [Security boffins harvest bumper crop of API keys from web](https://daily.dev/posts/security-boffins-harvest-bumper-crop-of-api-keys-from-web-56ku6ambh) · The Register · 0 upvotes · 0 comments
- [Nearly 1.5 million exposed secrets targeted in new revocation program](https://daily.dev/posts/nearly-1-5-million-exposed-secrets-targeted-in-new-revocation-program-xbpkiux6k) · BleepingComputer · 0 upvotes · 0 comments

---

Tags: [#security](https://daily.dev/tags/security), [#github](https://daily.dev/tags/github), [#appsec](https://daily.dev/tags/appsec)

[View this post on daily.dev](https://daily.dev/posts/over-543-000-valid-credentials-exposed-in-public-github-repositories-fblhmhuem)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Over 543,000 valid credentials exposed in public GitHub repositories","url":"https://daily.dev/posts/over-543-000-valid-credentials-exposed-in-public-github-repositories-fblhmhuem","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/over-543-000-valid-credentials-exposed-in-public-github-repositories-fblhmhuem"},"datePublished":"2026-09-30T18:11:00.067Z","dateModified":"2026-09-30T18:31:30.771Z","description":"A Truffle Security scan of 224 million GitHub repositories and over 58 billion files found 543,699 unique valid credentials exposed publicly as of July, with a...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/a89812fb70781e6e68af6e02923ad181?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/a89812fb70781e6e68af6e02923ad181?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"BleepingComputer","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"BleepingComputer","logo":"https://media.daily.dev/image/upload/s--as8nJ3qy--/f_auto,q_auto/v1774959951/logos/bleepingcomputer?_a=BAMAMiWQ0","url":"https://daily.dev/sources/bleepingcomputer"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/over-543-000-valid-credentials-exposed-in-public-github-repositories-fblhmhuem","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"security,github,appsec","timeRequired":"PT3M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"BleepingComputer","item":"https://daily.dev/sources/bleepingcomputer"},{"@type":"ListItem","position":3,"name":"Over 543,000 valid credentials exposed in public GitHub repositories"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/over-543-000-valid-credentials-exposed-in-public-github-repositories-fblhmhuem#faq","mainEntity":[{"@type":"Question","name":"How many valid credentials were found exposed in public GitHub repositories in a recent large-scale scan?","acceptedAnswer":{"@type":"Answer","text":"A scan of 224 million public GitHub repositories and over 58 billion files by Truffle Security found 543,699 unique valid credentials still working in July, appearing across more than 1.1 million files and repositories including forks. The median exposure time was 784 days, and about 10% of the credentials were older than 6.3 years, with the oldest dating to 2009. Anyone auditing repo hygiene can track findings like this credential exposure research on daily.dev."}},{"@type":"Question","name":"Does GitHub's Push Protection stop all types of leaked credentials?","acceptedAnswer":{"@type":"Answer","text":"No, Push Protection blocks only certain secret patterns by default, and 51.8% of the valid credentials found in a 2025 scan fell into categories it does not cover, such as database connection strings and Google API keys. Within the categories it does cover, exposure rates dropped 53% after GitHub enabled the feature by default for all users in February 2024. Teams configuring secret scanning coverage can follow ongoing analysis like this on daily.dev."}},{"@type":"Question","name":"Which types of leaked cloud credentials are most likely to still be active after being exposed on GitHub?","acceptedAnswer":{"@type":"Answer","text":"Google Cloud service account credentials had a high live rate: of 126,963 exposed, 69,041 were still valid and working. By contrast, npm tokens were almost always revoked, with only 1 of 101,886 committed tokens still functional, showing that revocation practices vary sharply by service and credential type. Developers deciding which secrets to prioritize rotating can keep up with findings like this on daily.dev."}}]}
```

