The research, conducted in November 2025, exposes an alarming trend in which developers inadvertently embed sensitive credentials directly into container images during the build process.
These exposed secrets include API keys for cloud services, database credentials, AI model tokens, and CI/CD pipeline access tokens, effectively providing attackers with authenticated pathways into production environments without requiring exploitation or credential cracking.
The investigation identified 10,456 container images harboring exposed secrets across 205 distinct Docker Hub namespaces.
After filtering for high and critical-severity findings, researchers successfully attributed 101 namespaces to identifiable organizations.
The exposure spans multiple sectors, with software development, financial services, and healthcare companies most prominently affected.
Perhaps most concerning: 42% of exposed images contained five or more secrets each. A single compromised container image could unlock entire cloud environments, CI/CD pipelines, and database systems simultaneously.
| Vulnerability Aspect | Details |
|---|---|
| Exposed Images | 10,456 Docker Hub images |
| Affected Namespaces | 205 distinct Docker Hub namespaces |
| Identified Organizations | 101 high/critical severity organizations |
| Images with 5+ Secrets | 42% of total exposed images |
| Most Exposed Credential Type | AI/ML API tokens (~4,000 exposed keys) |
| Credential Sources | OpenAI, Anthropic, Hugging Face, cloud providers |
| Exposure Duration | Months to years (75% keys not revoked) |
| Primary Attack Vector | Direct authentication using leaked credentials |
The research maps these exposures to a dangerous new attack paradigm: rather than exploiting vulnerabilities, attackers simply authenticate using credentials that were accidentally published.
This method entirely bypasses sophisticated perimeter defenses and multi-factor authentication safeguards.
Shadow IT accounts personal Docker Hub repositories used by contractors, freelancers, and employees emerged as a critical blind spot.
Organizations typically lack visibility into these accounts, creating months or even years of undetected exposure.
In one notable case, a Fortune 500 company’s secrets were exposed through a personal repository completely outside corporate monitoring systems.
The most common mistake involves embedding .env files containing secrets during Docker builds. While 25% of developers removed exposed credentials within one to two days, approximately 75% failed to revoke the underlying keys, leaving systems vulnerable long after the visible leak was addressed.
Security researchers recommend injecting secrets exclusively at runtime via environment variables, thereby eliminating the need for static credential storage in container images.
Find this Story Interesting! Follow us on Google News, LinkedIn and X to Get More Instant Update
The post Over 10,000 Docker Hub Images Found Leaking Production Credentials from 100+ Companies appeared first on Cyber Security News.
BROWNWOOD, Texas (KTAB/KRBC) - Families in Brownwood spent part of their spring break getting an…
I ran an experiment this week that I did not expect to be instructive, and…
Today's links Corrupt anticorruption: Notes from a target-rich environment. Hey look at this: Delights to…
Robotics How Pokémon Go Is Giving Delivery Robots an Inch-Perfect View of the WorldWill Douglas…
Digital communication is well beyond picture and prose. Nowadays viewers demand more interactive and human-like…
AI video generators are revolutionizing the film industry in 2026 by drastically reducing VFX budgets,…
This website uses cookies.