GitGuardian Launches Program to Warn Firms of Leaks
The Enterprise Good Samaritan Program alerts organisations to exposed credentials, whether or not they are GitGuardian customers.
Updated on Nov. 20, 2026 in Cybersecurity

GitGuardian has launched an Enterprise Good Samaritan Program to warn companies about exposed credentials found on public sources. The program is open to organisations whether or not they are GitGuardian customers.
Why it matters
Notices sent to individual developers do not always lead to exposed credentials being revoked, and only 35% of companies contacted about leaked credentials responded. About 90% of valid secrets remain active a week after the responsible developer has been alerted, leaving organisations exposed.
GitGuardian's systems screen more than 1 million public incidents each month and have detected over 83 million exposed secrets on public GitHub since 2018. The data does not show how many of the 3,913 linked credentials were ultimately revoked.
The players
GitGuardian
GitGuardian is a security company that monitors public code repositories and developer platforms for exposed secrets such as API keys and cloud credentials.
The details
GitGuardian contacts each organisation, usually reaching at least five people, and routes warnings to security teams and other internal contacts who can act on them. The company has sent 11.9 million alerts to 5.9 million developers. In May, a public GitHub repository containing CISA-related data and valid cloud credentials was identified, and it was taken offline within 26 hours of human escalation.
Timeline
May: CISA-related repository with valid credentials identified publicly.
Within 26 hours of human escalation: repository taken offline after CERT/CC escalation.
Earlier this month: Microsoft documented threat actors using agentic AI to search GitHub for credentials.
Since spring: GitGuardian linked 3,913 leaked credentials to 1,532 companies.
The Tech Race
The 28.65 million new secrets exposed on public GitHub in 2025, a 34% rise, show how the volume of leaked credentials on developer platforms is growing faster than many defences. GitGuardian's outreach positions a private firm as a remediation layer for code hosting services that have not themselves stopped leaks at source.
Developers and security teams whose organisations appear in GitGuardian's notices may need to rotate exposed credentials quickly, since most valid secrets stay active after an alert. Organisations that are not GitGuardian customers can still receive a warning through the program.
The takeaway
Treat any credential that has appeared in a public repository as compromised, and rotate it immediately rather than waiting for a warning. Confirm that your security team, not only individual developers, is the contact point for leak notices.
Further reading
For more on how exposed credentials are tracked across the web, see Cybersecurity coverage on Wisevoter.
Source note: This article includes information reported by SecurityBrief US.



