Skip to main content
Mallory
← Back to News
leaked-secret-api-keymass-credential-exposureai-platform-security

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

543,699 Exposed GitHub Credentials Remain Active and Enter AI Training Data

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.

Is this vendor in your chain?See attribution, scope, and your downstream exposure.
Check the blast radius
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

8 events · Jun 2009 – Jul 27, 2026
  1. Reported Oct 7, 20261mo ago

    Researchers find 221,000 valid credentials in Hugging Face AI-training data

    Truffle Security examined approximately 7.5 TB of AI-training data distributed through Hugging Face and reported approximately 221,000 valid credentials in that data.

    � GitHub �������� 543 ������ ����������� � ������������ ����������� �������, ������ � �������
  2. Reported Oct 1, 20262mo ago

    Researchers detail push-protection gaps and live Gemini API keys

    Truffle Security reported that 51.8% of the 543,699 still-valid exposed credentials used formats not blocked by default GitHub push protection, including connection strings, private keys, and Google API keys. The researchers found 33,343 live Google API keys—31,374 authenticated to Gemini—and observed far higher survival rates for database credentials than for tokens automatically revoked by npm, GitHub, and Hugging Face.

    Half a Million GitHub Credentials Are Still Active, Most Have Been Sitting in the Open for Years - CySecurity News - Latest Information Security and Hacking Incidents
  3. Jul 27, 20264mo ago

    Researchers found 543,699 exposed GitHub credentials still active

    Truffle Security tested credentials linked to 1,103,438 public exposures and found 543,699 unique credentials that still authenticated. The active set included Google Cloud service-account credentials, MongoDB connection strings, and Google API keys, showing that exposed secrets can remain usable for years and persist in downstream training data.

    500,000 Active Credentials Left Exposed on GitHub - SecurityWeek
  4. Aug 7, 20251y ago

    The Stack v3 crawl of public GitHub repositories concluded

    The Stack v3 dataset crawl ended after collecting code from 224,553,295 public GitHub repositories. The 15.9 TB dataset was used for code-focused AI-model training and later credential-persistence analysis.

    Over 543,000 GitHub Credentials Remain Active After Being Publicly Exposed
  5. Feb 2024

    GitHub enabled push protection by default for free users

    GitHub began enabling push protection by default for free users. The feature blocks recognizable secrets before publication, although developers can remove or bypass warnings and it does not remediate older commits.

    Over 543,000 GitHub Credentials Remain Active After Being Publicly Exposed
  6. Feb 2023

    GitHub made secret-scanning alerts free for public repositories

    GitHub made secret-scanning alerts available at no cost for public repositories, enabling detection of historical credential exposures for repository owners.

    Over 543,000 GitHub Credentials Remain Active After Being Publicly Exposed
  7. Apr 2022

    GitHub introduced Push Protection for Advanced Security users

    GitHub introduced Push Protection for Advanced Security users, detecting supported API keys, access tokens, and other secrets in code and blocking their publication.

    Репозитории на GitHub раскрывают более 543 000 учетных данных - Хакер
  8. Jun 2009

    Oldest still-valid credential entered a GitHub file

    A database credential later found to remain valid was in an Erlang server configuration file last modified in June 2009. The credential was still usable when researchers tested it in 2026.

    Over 543,000 GitHub Credentials Remain Active After Being Publicly Exposed
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Affected products

1 linked
Github

Organizations

1 linked
GitHub
Do you run this?See attribution, scope, and whether this vendor sits anywhere in your supply chain.
Get the Full Incident Picture
Source coverage

Sources

10 references tracked. Mallory keeps watching after this page renders.

Truffle Security BlogNews · Oct 23, 2026
GitHub Repos Exposed 543,699 Credentials. Nobody Revoked Them. ◆ Truffle Security Co.Open source ↗
Opennet RuNews · Oct 7, 2026
� GitHub �������� 543 ������ ����������� � ������������ ����������� �������, ������ � �������Open source ↗
OpennetNews · Oct 7, 2026
� GitHub �������� 543 ������ ����������� � ������������ ����������� �������, ������ � �������Open source ↗
XakepNews · Oct 6, 2026
Репозитории на GitHub раскрывают более 543 000 учетных данных - ХакерOpen source ↗
2 additional sources from 03-10-2026 to 03-10-2026
Cysecurity NewsNews · Oct 1, 2026
Half a Million GitHub Credentials Are Still Active, Most Have Been Sitting in the Open for Years - CySecurity News - Latest Information Security and Hacking IncidentsOpen source ↗
Malware NewsNews · Oct 1, 2026
Credenziali GitHub esposte anche nei dataset per l’addestramento dell’IA - Malware News - Malware Analysis, News and IndicatorsOpen source ↗
Security WeekNews · Oct 1, 2026
500,000 Active Credentials Left Exposed on GitHub - SecurityWeekOpen source ↗
Cyber Security NewsNews · Oct 1, 2026
Over 543,000 GitHub Credentials Remain Active After Being Publicly ExposedOpen source ↗
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.