Starting November 21, 2025, a second wave of the Shai-Hulud worm compromised around 700 packages on npm, the main software library for JavaScript projects. Affected packages include projects published by Zapier, ENS, PostHog and Postman. The attack created more than 25,000 GitHub repositories filled with stolen secrets.

What is going on

Most modern websites and apps are built from thousands of small code packages written by other people. npm is the shop where those packages are downloaded from. Shai-Hulud is a worm: malicious code that spreads on its own from one package to the next.

This version runs during the preinstall phase, the moment before a package is even unpacked, using a loader built on the Bun JavaScript runtime. It searches the machine for access keys and tokens, then publishes them into new public GitHub repositories. Hundreds of leaked GitHub, AWS, Google Cloud and Azure credentials have already been found.

Think of a delivery that opens itself on your doorstep, copies your house keys, and posts the copies on a public noticeboard.

Diagram showing how the Shai-Hulud worm steals credentials during npm preinstall and where pinning stops it
The worm runs before a package is unpacked, so stopping it means pinning versions and rotating keys.

Who is affected

Anyone who installed one of the affected package versions after November 21, 2025 is at risk. That includes your own developers, your agency, and any build server that installs packages automatically.

If your site is a plain WordPress or Shopify site with no custom JavaScript build step, you are unlikely to be directly affected. If a developer builds or deploys your site from source code, ask them to check.

What to do now

  1. Ask who installs your code. Contact your developer or agency and ask whether any npm install ran after November 21, 2025.
  2. Clear npm caches. Cached copies of a bad package can be reinstalled later, so the cache needs to be emptied.
  3. Pin dependencies to pre-November 21 versions. Lock each package to a version published before that date until clean releases are confirmed.
  4. Rotate all credentials. Replace GitHub tokens, AWS, Google Cloud and Azure keys, and any other secret stored on affected machines.
  5. Look for unknown GitHub repositories in your accounts and organisations, and remove any you did not create.

How to check your own site

A website scan cannot see inside your developer's laptop, but it can show what a stolen key might expose. The free Website Security Check flags outdated CMS versions, known-vulnerable plugins, missing security headers, weak TLS and email-authentication gaps. On a site you own and have verified, you can also run a full scan, which adds active OWASP Top 10 testing, port and service checks with CVE matching, CMS deep scans, and exposed-file and secret checks.

Source: Wiz: Shai-Hulud 2.0 ongoing supply chain attack, November 2025.