Self-replicating worm compromises hundreds of npm packages
A malicious worm is stealing developer credentials from npm packages to infect more libraries, so you must rotate your keys and pin your dependencies.
What happened
Attackers released a self-replicating worm that steals developer tokens and cloud keys from local environments. These stolen credentials were used to republish over 500 legitimate npm packages with malicious code, which then spread the infection further. The stolen data appeared in public GitHub repositories before being used for subsequent attacks.
Who is affected
Any developer who installed or updated npm packages between mid-September and late September 2025 may have compromised their environment. Because the worm targets common build tools, teams using automated CI/CD pipelines are at higher risk of leaking sensitive keys. You are vulnerable if your project relies on any of the 500 affected libraries.
Why it matters if you build with AI
AI agents often pull the latest versions of packages to satisfy dependencies, which makes them a primary vector for this type of supply-chain attack. If your AI tools have permission to write to your repositories, they might inadvertently commit stolen secrets or spread infected code. Monitor your agent logs for unusual outbound traffic to public sites.
What to do
- Rotate all npm, GitHub, and cloud keys
- Enable phishing-resistant MFA
- Turn on secret scanning and Dependabot
- Pin dependencies to versions from before 2025-09-16
Locaas is being built to track advisories like this, check your running applications and propose the necessary updates for your approval.
Get early access