InformationalEcosystem changeOngoing

GitGuardian Good Samaritan Program now warns enterprises of leaked secrets

GitGuardian extended its Good Samaritan Program to enterprises; set up a security.txt file and a monitored security inbox to receive its warnings.

Published
Updated
Exploitation
Not confirmed for any specific incident. The press release cites a Microsoft-documented case of attackers using agentic AI to search public GitHub repositories for exposed credentials, which the sources do not detail.

What happened

GitGuardian announced the Enterprise Good Samaritan Program on November 16, 2026, according to the press release carried by GBHackers and Hackread. Both outlets republished the same CyberNewswire release. Hackread’s page header is dated November 17, while its text uses the November 16 dateline. This is a vendor announcement, not an independent investigation, so every figure below is GitGuardian’s own.

Reported details:

  • The program expands GitGuardian’s responsible disclosure work. It uses AI-assisted attribution and human review to trace high-impact credential leaks to the affected company and send disclosures to that company’s security team. GitGuardian says it can now do this for any company, whether or not it is a customer.
  • The original Good Samaritan Program has, since 2018, detected more than 83 million exposed secrets on public GitHub. It sent 11.9 million alerts to 5.9 million developers.
  • GitGuardian says approximately 90% of valid secrets remain unrevoked a week after the responsible developer is alerted.
  • The Enterprise program has linked more than 3,913 high-impact leaks to 1,532 companies. GitGuardian says it typically reached at least five people at each organization.
  • GitGuardian monitors public sources including GitHub and Docker Hub. Its AI agents screen more than 1 million public incidents each month and investigate over 100,000 in depth. Human experts review high-impact findings before disclosure.
  • Only 35% of contacted organizations responded to the outreach.
  • GitGuardian’s 2026 State of Secrets Sprawl report, as cited in the release, found 28.65 million new secrets exposed on public GitHub in 2025, a 34% year-over-year increase.
  • In May 2026, GitGuardian says a public GitHub repository with sensitive CISA-related data and valid cloud credentials stayed online after nine automated alerts. After escalation through CERT/CC and established contacts, it was taken offline within 26 hours.
  • The release says Microsoft documented attackers using agentic AI to search public GitHub repositories for exposed credentials in November 2026. In one observed case, an AI agent went from searching for a leaked secret to extracting data from Azure Key Vault in five minutes. The release does not link to Microsoft’s report, and the sources do not give more detail.

No CVE, software flaw or patch is involved.

Am I affected?

Not confirmed for any named organization. The sources do not list the 1,532 companies. Your organization could be affected if its credentials appear in public sources such as GitHub or Docker Hub.

The release says organizations receive the full details of their exposures without signing up or becoming customers. It also says GitGuardian offers a GitHub Security Audit to assess exposure on public GitHub. Neither source gives a URL for these pages, so we do not link to them.

What to do now

  1. Publish a security.txt file and staff a monitored security inbox. GitGuardian calls for exactly this so external researchers can reach the right people.
  2. Make sure the people behind that inbox can act on a disclosure. The release says developers are often not the ones able to revoke a leaked credential.
  3. If you receive a disclosure, review the details provided and revoke any credential it identifies. The release’s stated aim is to get exposed credentials to the teams that can revoke them.
  4. Consider using GitGuardian’s GitHub Security Audit to assess your exposure on public GitHub, as the release suggests. The sources give no further detail on how it works.

Sources