A credential-stealing worm distributed through npm compromised hundreds of packages in early August 2026, marking one of the registry's largest supply chain attacks. The malware first appeared in keyv@6.0.0 before spreading into 79 confirmed package names across multiple organizations, according to SafeDep's analysis. Broader monitoring estimates placed the total footprint at 353 poisoned package names, with Aikido reporting at least 868 affected packages.

The worm installs hooks into Claude Code and Visual Studio Code environments, enabling attackers to exfiltrate credentials and intercept developer workflows. Developers who installed compromised versions risked exposing authentication tokens, API keys, and other sensitive data stored in their development environments. The attack leveraged npm's namespace system to propagate rapidly beyond the initial Keyv package family into unrelated projects.

The scale of this attack underscores persistent vulnerabilities in open source distribution. Attackers compromised a foundational dependency that organizations trusted implicitly. Once inside the supply chain, the malware spread through transitive dependencies, reaching downstream consumers who never directly installed the poisoned package.

Organizations relying on npm packages need immediate remediation. Steps include auditing package.json files and lock files for compromised versions, revoking any exposed credentials, and scanning for unauthorized VS Code or Claude Code hook modifications. npm has since removed malicious versions, but organizations must verify their installations against the confirmed list of poisoned package names.

This incident demonstrates how widely trusted dependencies can become vectors for widespread compromise. The attack targeted developers' local machines rather than production infrastructure, making detection harder. Security teams should implement stricter dependency management policies, including package signature verification where available and regular audits of transitive dependencies. Monitoring for unexpected modifications to IDE configurations provides another layer of detection.

The npm ecosystem remains under sustained pressure from supply chain attackers. Organizations cannot rely solely