ChainDrop worm crawls into npm supply chain, evades standard defenses
A new variant of the Shai-Hulud npm worm, dubbed ChainDrop, has compromised hundreds of software packages and introduced stealthier ways to spread. It matters because it can infect developers’ projects and automated build systems without leaving obvious malicious changes in source-code repositories, making routine reviews less effective.
Researchers identified the attack on 4 August, finding 444 affected packages from multiple publishers with combined monthly downloads of about two billion; targets included keyv, flat-cache and cache-manager. ChainDrop steals npm, GitHub and cloud credentials, then modifies package tarballs and adds VS Code or Claude Code configuration hooks that can run when an infected branch is opened. It can use stolen npm tokens to republish altered packages and GitHub access to commit malicious configuration files across accessible repositories and branches.
In short
- ChainDrop infected 444 npm packages and evades normal repository checks.
- It spreads through altered tarballs and developer-tool configuration hooks.
- Stolen credentials can fuel further package and repository compromises.
Explained simply
npm is a service developers use to share and install packages, which are reusable pieces of software for building projects. Many projects and automated systems rely on packages published by other people, so a change to a widely used package can affect many users downstream.
The Shai-Hulud worm is malicious software that spreads by stealing developers’ account credentials and using them to alter and republish packages. ChainDrop is a reported variant linked to hundreds of packages, including tools used by other software; it can also add configuration files that run code when a developer opens an affected project.
The incident matters because the changes may be hidden in package downloads or project settings rather than obvious edits to source code. That can make ordinary code reviews less likely to spot them, while stolen access could let the worm spread to further packages and repositories.