Find notable cyber news and cases, enriched with sources, timelines, and signals.

GitLab Cloud public repositories secret exposure

Data Leak
First reported
Last updated
Happening score
H score 52
1 unique sources, 1 articles

Summary

Hide ▲

A scan of 5.6 million public GitLab Cloud repositories uncovered 17,430 verified live secrets, creating a large-scale credential exposure risk across 2,804 unique domains. The exposed material included API keys, passwords, tokens, and other high-value cloud credentials. Some secrets dated back to 2009 and were still valid. Many organizations revoked exposed credentials after notification, but some secrets remained live.

Related Happenings

Congress demands CISA answers on GitHub credential leak

Public Sector Action
H score19 First: 22.05.2026 19:34 Last: 22.05.2026 19:34 Sources 1

About this happening: Lawmakers in both houses of Congress demanded answers from CISA after a contractor exposed AWS GovCloud keys and other secrets on public GitHub. The letters presse...

Google Cloud Platform API key revocation testing finds minutes-long post-deletion authentication

Technical Analysis
H score16 First: 21.05.2026 23:07 Last: 21.05.2026 23:07 Sources 1

About this happening: Testing showed deleted Google Cloud Platform API keys could still authenticate for minutes after revocation, creating a post-deletion abuse window that weakens incident...

CISA contractor GitHub repository exposed internal credentials

Data Leak
H score28 First: 18.05.2026 23:48 Last: 18.05.2026 23:48 Sources 1

About this happening: A CISA contractor left a public GitHub repository exposing AWS GovCloud credentials, plaintext passwords, and other internal access material tied to CISA and *...

Latest development: 10.07.2026 19:00

CISA said that within moments of receiving information about internal AWS GovCloud keys and other material in a public GitHub repository owned by a contractor, its Office of the Chief Information Officer took swift and comprehensive action to mitigate exposure to CISA cloud resources and code repositories. The agency said internal incident response began on May 15, no customer or mission data was exposed, and the leaked credentials were not used outside CISA's environments.

Moltbook Supabase database exposure

Data Leak
H score45 First: 08.02.2026 09:32 Last: 08.02.2026 09:32 Sources 1

About this happening: A misconfigured Supabase database exposed Moltbook data, putting API authentication tokens, email addresses, and private messages at risk of unauthorized acces...

Docker Hub container images leaking secrets across more than 100 organizations

Data Leak
H score35 First: 04.02.2026 17:05 Last: 04.02.2026 17:05 Sources 1

About this happening: Researchers uncovered more than 10,000 Docker Hub container images leaking production API keys, cloud tokens, CI/CD credentials, and AI model access tokens, putting secret...

Timeline

  1. 28.11.2025 19:43 2 articles · 7mo ago

    Public GitLab Cloud repository secret scan and disclosure

    Initial Disclosure

    Luke Marshall used a GitLab public API endpoint and a custom Python script to enumerate every public GitLab Cloud repository, pushed 5.6 million non-duplicate repository names through AWS Simple Queue Service (SQS), and ran TruffleHog in AWS Lambda with concurrency set to 1000. The scan completed in just over 24 hours for $770 and identified 17,430 verified live secrets across 2,804 unique domains, including over 5,200 Google Cloud Platform (GCP) credentials and a little over 400 GitLab keys. Automated notifications were sent to affected parties, many organizations revoked exposed secrets, and some secrets remained live on GitLab.

    Show sources