Shai-Hulud 2.0: the npm worm returns and spreads through GitHub
A supply chain attack used malicious scripts to steal credentials from hundreds of npm packages and you should act if you use external dependencies.
What happened
Attackers published hundreds of malicious npm packages containing scripts that run automatically during installation. These scripts stole developer credentials for GitHub and major cloud providers, then used them to create thousands of fake repositories. This automated worm spread by impersonating legitimate software and contributors.
Who is affected
Developers who installed affected packages from Zapier, PostHog or Postman between 21 and 24 November 2025 are at risk. The attack targeted users of nearly 800 npm packages and 25,000 GitHub repositories, which resulted in significant data leaks. You are affected if your build environment ran these malicious preinstall scripts.
Why it matters if you build with AI
AI coding tools often suggest or install dependencies automatically to solve specific tasks, which can introduce risks if the packages are not verified. If these tools pull in compromised packages, your local machine or CI environment could leak sensitive cloud keys. This attack shows how one malicious dependency can compromise your entire development pipeline.
What to do
- Disable npm install lifecycle scripts in your CI environment
- Rotate all npm, GitHub and cloud provider credentials
- Switch to short-lived scoped tokens for all automated deployments
Locaas is being built to track advisories like this, check your running applications and propose the necessary updates for your approval.
Get early access