Skip to content
Cloud Security Breaches

GitHub (npm registry) (2025): what the sources say about the cloud incident

GitHub (npm registry) disclosed the incident on 22 Sep 2025. What was exposed, as the sources state it: The 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.

Open the ledger · Report a correction

Disclosed
22 Sep 2025
Incident window
notified September 14, 2025, as the post says
Cloud or provider
GitHub
What was exposed
The 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.
How access was gained
GitHub stated that a self-replicating worm spread through compromised maintainer accounts by injecting malicious post-install scripts into popular packages.
Access path
Stolen user credentials and session tokens; also Leaked access keys and secrets
Kind of control that addresses it
require phishing-resistant multi-factor authentication and short-lived scoped tokens for package publishing and disable install scripts by default

In the words of the source

“a self-replicating worm that infiltrated the npm ecosystem via compromised maintainer accounts by injecting malicious post-install scripts into popular JavaScript packages.” (provider post mortem, Our plan for a more secure npm supply chain)

Primary sources

If a field is wrong or a newer primary source exists, write to the editor with the entry name in the subject.

Sources

  1. Our plan for a more secure npm supply chain, read 16 Nov 2026

Last reviewed 16 Nov 2026.