A recent variant of the Shai-Hulud npm worm, referred to as ChainDrop, has been identified as a significant threat within the npm supply chain, affecting 444 packages. This malware employs advanced techniques to propagate while evading standard security measures.
Incident Overview
On August 4, security researchers reported a large-scale attack utilizing the ChainDrop variant, which has infected packages that are collectively downloaded approximately 2 billion times each month. The attack specifically targeted critical infrastructure dependencies, including keyv, flat-cache, and cache-manager.
Propagation Techniques
ChainDrop distinguishes itself from typical malware by using unconventional methods to infiltrate open source repositories. Notably, it can infect systems even if users do not directly install compromised packages. Once activated, the worm inserts startup hooks into repository configuration files. This means that merely opening an infected Git branch in development environments like VS Code or Claude Code can trigger the worm, allowing it to take control of the repository.
Data Theft and Self-Replication
The malware scans the user’s workspace for npm tokens and other sensitive credentials, including cloud keys. It then encrypts any stolen data and sends it to attacker-controlled endpoints. If it finds an npm token, ChainDrop can download tarballs of all accessible packages, effectively rebuilding them to include its malicious payload. This method allows it to propagate without leaving traces in the source code repository.
Mitigation and Response
In response to the attack, all infected packages have been removed from npm. Developers are advised to check for unauthorized files such as .claude/settings.json and .vscode/tasks.json across all branches of their repositories. Open source security firm SafeDep has provided a list of the compromised packages and their version numbers for developers to verify against their current installations. Security experts suggest that organizations reassess their security measures, particularly regarding trusted publishing tools like GitHub Actions, to prevent similar breaches in the future.
This article was produced by NeonPulse.today using human and AI-assisted editorial processes, based on publicly available information. Content may be edited for clarity and style.
