ChainDrop worm crawls into npm supply chain, evades standard defenses

A new variant of the Shai-Hulud npm worm, named "ChainDrop" by Microsoft and others, has infiltrated hundreds of packages and evaded standard defenses. This malicious software, discovered on August 4, infected 444 packages from multiple publishers and targeted deeply embedded infrastructure dependencies such as keyv, flat-cache, and cache-manager.

These packages are collectively downloaded about 2 billion times monthly. ChainDrop propagates stealthily by placing startup hooks into repository configuration files, which can be triggered simply by opening an infected Git branch in VS Code or Claude Code. This allows ChainDrop to control the repository without leaving evidence of tampering.

Once executed, ChainDrop searches for npm tokens with full write privileges, as well as other credentials like cloud keys and secrets, in shell configurations, environment variables, and live memory. If it finds an npm token, it downloads the tarballs of all packages that token has full access to, bypassing the repositories themselves.

ChainDrop also searches for GitHub credentials and commits malicious configuration code directly into accessible repositories. This attack is particularly dangerous because npm is widely integrated into automated CI/CD pipelines, allowing the worm to infiltrate fresh builds. To mitigate the threat, developers should check for unauthorized files in their repositories and review all branches.

They should also reconsider their dependency scanning tools and treat repository-supplied configuration as executable content.