Cloud Threat Landscape
  • Incidents
  • Actors
  • Techniques
  • Defenses
  • Tools
  • Targeted Technologies
  • Posters & Newspapers
  • About
  • RSS
  • STIX
  • Back to wiz.io

Made with đź’™ by Wiz

Last Updated: April 3, 2025

Cloud Threat Landscape
/Incidents
Incidents
/
GitHub & npm incident

GitHub & npm incident

Type
Incident
Actors
❓Unknown
Pub. date
April 15, 2022
Initial access
End-user compromise
Impact
Supply chain attackData exfiltration
References
https://status.heroku.com/incidents/2413https://support.travis-ci.com/hc/en-us/articles/4693410985500-SECURITY-BULLETIN-Customer-repositories-have-NOT-been-accessed-https://blog.heroku.com/april-2022-incident-reviewhttps://github.blog/2022-04-15-security-alert-stolen-oauth-user-tokens/
Status
Finalized
Last edited
Jun 2, 2024 11:54 AM

On April 12, 2022, GitHub Security began an investigation that uncovered evidence that an attacker abused stolen OAuth user tokens issued to two third-party OAuth integrators, Heroku and Travis-CI, to download data from dozens of organizations, including npm.

According to GitHub's investigation, between April 7-10, 2022, the attacker initially authenticated to the GitHub API using the stolen OAuth tokens issued to Heroku and Travis CI. For most people who had the affected Heroku or Travis CI OAuth apps authorized in their GitHub accounts, the attacker listed all the user’s organizations. Then, the attacker then selectively chose targets based on the listed organizations, listed the private repositories for user accounts of interest, and then proceeded to clone some of those private repositories.

image