Leaked GitHub App Keys Still Authenticate as Hundreds of Apps
Breach & Incident Intelligence · 3 sources · Updated 2mo ago · First seen Sep 23, 2026

GitGuardian found 474 publicly exposed GitHub App RSA private keys that still authenticated as 440 distinct apps out of 4,802 GitHub-context keys examined. Because GitHub App private keys can remain valid indefinitely, an attacker with a leaked key can mint API tokens indistinguishable from those issued by the legitimate app and impersonate it.
The valid credentials included keys linked to a shared GitHub Actions token app, CDC-related infrastructure, BuildBuddy, and the unmaintained Crusher.dev framework. Affected apps could retain access to private repositories and permissions to modify code, administer organizations, manage self-hosted runners, or control workflows; organizations should rotate exposed App keys immediately and continuously monitor public sources for credential leaks.

