GitGuardian detected 28.65 million new hardcoded secrets in public GitHub commits in 2025

Secrets are leaking 1.6× faster than the developer population is growing since 2021.

Publicly active developers on GitHub grew at twice the usual rate

Public GitHub is growing fast, but it’s also rapidly renewing: 54% of active developers made their first commit in 2025, increasing the volume of newly created code and integrations, and with it, the risk of exposed credentials.

Developer workstations are now a prime target for secrets theft

of compromised machines held more than 10 secrets, and 5% carried over 100.

59% of compromised machines were CI/CD runners rather than personal workstations, this exposure extends well beyond the individual developer into shared build infrastructure.

AI adoption creates new credential security risks

AI-service secrets exposed

YoY growth of secrets of AI-related services

Credentials for AI services are accelerating faster than any other category. As teams adopt new AI tools, they also create more tokens, keys, and service identities, often without equivalent governance. These leaks are also more likely to slip through controls designed around traditional developer workflows.

AI-assisted commits significantly contribute to secrets sprawl

AI-assisted development moved from experiment to default. Code production accelerated, and credential exposure rose with it.

Claude Code co-authored commits leak secrets at ~2× the baseline across all Public GitHub commits but the human factor remains also critical.

2025 showed a clear acceleration starting early in the year, followed by a steep ramp in the second half of the year as multiple assistants gained adoption.

Exposed credentials remain a major, repeatable path to compromise. AI-assisted development has moved from experiment to default, and credentials are now leaking at every layer of the stack.

MCP configuration files routinely expose secrets

In early 2025, the Model Context Protocol (MCP) emerged as the new standard to connect to LLMs with external tools and data sources such as APIs, providers, or collaboration platforms. Our research found 24,008 unique secrets exposed in MCP configuration files.

of all secrets leaked in MCP configuration files are PostgreSQL DB connection strings.

Top secret types map directly to common API platforms and web- tooling, data access layers, and developer productivity services.

Internal repositories remain the biggest exposure reservoir

Internal repos are 6× more likely than public ones to contain hardcoded secrets.

These exposed secrets are also now at risk of accidental public exposure by AI coding assistants.

Public repositories that contain at least one secret

Internal repositories that contain at least one secret

One in four leaks originates outside of code repositories

Secrets sprawl extends beyond code: ~28% of incidents originate from leaks in collaboration and productivity tools (not just repositories), where credentials can be exposed to broader audiences, automations and AI agents.

of secrets sprawl happens exclusively outside of code repositories. Only 4% appear in both.

Collaboration tools incidents are more severe with more than half being critical.

Secrets exposed in code alone are very different from those exposed through collaboration tools, meaning that scanning only the code will miss a meaningful portion of leaks.

Prioritization based only on secret validation is fundamentally flawed

of critical secrets leaked lack validation checkers

Generic secrets (unstructured credentials such as passwords, private keys, or custom tokens) drive most high-risk incidents but can't be validated. Prioritization based only on validation creates blind spots (46% missed) and wasted effort (many validated secrets are low-impact). You can't fix what you can't see. Without comprehensive context, teams still fail to remediate them.

The majority of leaked secrets remain exploitable for years

Teams can't rotate secrets without risking production outages—so they don't.

We tracked valid secrets detected in 2022. Four years later,

are still active and exploitable, sitting in public repositories.

The problem isn't detection. It's remediation.

Detection without governance leaves secrets sprawl unsolved

The industry is still in the early stage of addressing with the massive debt of secrets sprawl accumulated over the years, emphasizing the importance of AI-led remediation, prevention, and deception.

The dominant issue: long-lived secrets.

Creation velocity is outpacing identity maturity

Duplication & internal leakage together make up nearly a third of issues (33%).

Establish a New Standard for Secrets Security

Security risk is not binary. A credential that validates successfully is not necessarily dangerous, and a secret with no validation checker is not necessarily safe.

In 2026, effective secrets security requires four capabilities working together:

Understanding what each secret unlocks

Assessing privilege, scope, and exposure

Prioritizing based on actual business impact

Addressing the long tail, not just the validated minority

"The difference between success and failure isn't finding more secrets, it's knowing which ones to fix first."

#1 Security App on the GitHub Marketplace

%nggsu%,000 developers already use GitGuardian to prevent committing secrets and to detect compromise with honeytokens, making it the #1 security app on the GitHub marketplace.

Download the State of Secrets Sprawl 2026 report to establish a new standard for secrets security.