In September 2025, a self-spreading program called Shai-Hulud worked its way through more than 500 packages in the npm ecosystem, the code library that most modern websites and apps are built from. It stole GitHub tokens and cloud keys from developer machines, then used the stolen publishing credentials to inject itself into further packages automatically. The US cybersecurity agency CISA issued an alert about the compromise on 23 September 2025.

What is going on

Most websites are not written from scratch. Developers assemble them from small pieces of shared code called packages, downloaded from npm, a public library of those pieces.

Shai-Hulud is a worm, meaning it copies itself without anyone steering it. Once installed on a developer machine, it searched for secrets: GitHub access tokens and cloud keys. It then used any npm publishing credentials it found to push an infected version of that developer's own packages.

Think of a shared pantry. One contaminated jar is used in someone else's recipe, that batch goes back on the shelf, and the problem spreads by itself rather than by one person acting again and again.

Diagram showing how the Shai-Hulud worm steals developer credentials and republishes infected npm packages, and where pinning stops it
The worm turns one stolen npm token into new infected packages; pinned lockfiles and rotated credentials break the loop.

Who is affected

Any business whose website or app installs npm packages is in scope, along with the developers who build it and the automated build systems, known as CI, that assemble and deploy it.

The two main risks are credential theft, where access tokens and cloud keys are taken, and supply-chain compromise, where bad code reaches your site through a trusted update. If your site is a plain hosted CMS with no custom build step, you are far less likely to be affected.

What to do now

  1. Ask your developer or agency whether your site or app installs npm packages, and when it last built.
  2. Audit your lockfiles, the files that record exactly which package versions were installed, and pin them to versions published before 16 September 2025.
  3. Rotate developer credentials: GitHub tokens, npm tokens and cloud keys used on developer machines and in CI.
  4. Enforce phishing-resistant multi-factor authentication on GitHub, npm and cloud accounts, so a stolen password alone is not enough.
  5. Review recent deployments and account activity for changes nobody on your team made.

How to check your own site

A scan cannot see inside your build pipeline, but it can show what the outside world sees. The free Website Security Check flags outdated CMS versions, known-vulnerable plugins, missing security headers, weak TLS and email-authentication gaps. If you want deeper coverage of your live site, you can run a full scan, which adds active OWASP Top 10 testing, port and service checks with CVE matching, WordPress and Magento deep scans, and exposed-file and secret checks, only against sites whose ownership you have verified.

Source: CISA alert on the npm supply chain compromise, September 2025.