Skip to content
Cloud Security Breaches

Cloud breaches involving GitHub: 9 in the ledger

9 incidents in the ledger involve GitHub. The most common access path among them is stolen user credentials and session tokens. The earliest was disclosed in 2022 and the latest in 2026. Each incident links to its company statement, filing, court document or post-mortem.

Open the ledger · All providers

DisclosedOrganizationAccess pathWhat was exposed
2026-05-08SailPoint, Inc.Third-party accessA subset of the company’s GitHub repositories; the filing says no evidence that customer data in production or staging environments was accessed, and customers with information in the accessed repositories were notified.
2025-09-22GitHub (npm registry)Stolen user credentials and session tokensThe post says 500+ compromised packages were removed from the npm registry and that the worm could steal multiple types of secrets, not just npm tokens.
2025-08-26Nx (Nrwl)Leaked access keys and secretsThe company's npm publishing token; malicious package versions scanned users' systems and uploaded results to public GitHub repositories. The company stated Nx Cloud was not affected.
2023-03-23GitHubLeaked access keys and secretsThe company stated GitHub.com's RSA SSH private key was briefly exposed in a public GitHub repository; it stated it had no reason to believe the key was abused and that no GitHub systems or customer information were compromised.
2022-12-31SlackStolen user credentials and session tokensThe company stated that private code repositories were downloaded, that they contained no customer data, means to access customer data or Slack's primary codebase, and that the production environment was not accessed.
2022-11-01DropboxStolen user credentials and session tokensThe company stated that the threat actor copied 130 code repositories containing some credentials (primarily API keys) and a few thousand names and email addresses; no customer content, passwords or payment information was accessed.
2022-09-16GitHub users (phishing campaign reported by GitHub)Stolen user credentials and session tokensGitHub stated that the campaign affected many victim organizations, and that in many cases the threat actor downloaded private repository contents accessible to the compromised user; GitHub itself was not affected.
2022-04-21GeniusU Pte. Ltd.Leaked access keys and secretsThe PDPC decision states about 1.26 million users' first and last name, email address, location and last sign-in IP address were accessed and exfiltrated from a staging application database.
2022-04-15Heroku (Salesforce) and Travis CI OAuth tokensThird-party accessGitHub stated that stolen OAuth user tokens issued to Heroku and Travis CI were used to download data from dozens of organizations, including npm; Heroku stated the actor also downloaded stored customer GitHub integration tokens and a database of pipeline-level config variables.

How access was gained, entry by entry

  • SailPoint, Inc.: The filing says the company detected unauthorized access to a subset of its GitHub repositories and that the root cause was a vulnerability in a third-party application, which it does not name.
  • GitHub (npm registry): GitHub stated that a self-replicating worm spread through compromised maintainer accounts by injecting malicious post-install scripts into popular packages.
  • Nx (Nrwl): The post-mortem says attackers exploited a GitHub Actions injection vulnerability to steal the npm publishing token; the repository's workflow permissions were read and write.
  • GitHub: The company stated the exposure resulted from what it believes was an inadvertent publishing of private information.
  • Slack: The company stated that a limited number of employee tokens were stolen and misused to reach its externally hosted GitHub repository, and that a third-party vendor was compromised.
  • Dropbox: The company stated that employees received phishing emails impersonating a CI service, and that a fake login page collected GitHub credentials and a one-time code, giving the threat actor access to one GitHub organization.
  • GitHub users (phishing campaign reported by GitHub): GitHub stated that a phishing site imitating the GitHub login page stole credentials and relayed TOTP codes to the threat actor in real time, and that accounts protected by hardware security keys were not vulnerable.
  • GeniusU Pte. Ltd.: The decision says the likely cause was a compromise of a developer's GitHub password, which let the threat actor into the company's GitHub environment; database login credentials had been stored in the codebase there, so the actor reached and exfiltrated the database. The staging database held real personal data.
  • Heroku (Salesforce) and Travis CI OAuth tokens: Heroku stated that initial access to its environment was obtained by using a compromised token for a Heroku machine account, after which stored customer GitHub integration OAuth tokens were downloaded; GitHub stated the tokens were then abused against GitHub.com.

Sources

  1. SailPoint, Inc., read 16 Nov 2026
  2. GitHub (npm registry), read 16 Nov 2026
  3. Nx (Nrwl), read 16 Nov 2026
  4. GitHub, read 16 Nov 2026
  5. Slack, read 16 Nov 2026
  6. Dropbox, read 16 Nov 2026

Last reviewed 16 Nov 2026.