A malicious credential-stealing worm has infiltrated the npm registry, infecting hundreds of packages across various organizations. According to The Hacker News, the campaign first surfaced within the keyv@6.0.0 release on August 4, 2026, before expanding its reach into the Cacheable namespaces and beyond. The malware is designed to install hooks into both Claude Code and VS Code environments to facilitate unauthorized data exfiltration.
Security researchers have provided varying assessments of the infection's scope based on their internal monitoring tools. SafeDep, which conducted an analysis of the registry, confirmed the presence of 353 poisoned versions across 79 distinct package names. Other monitoring services suggest a more pervasive footprint. While SafeDep tracks the incident at 442 versions across 353 names, external reporting from Aikido has identified at least 868 compromised packages affected by this ongoing distribution effort.
Incident Scope and Data
| Assessment Source | Affected Versions | Affected Package Names |
|---|---|---|
| SafeDep (Verified) | 353 | 79 |
| SafeDep (Monitoring) | 442 | 353 |
| Aikido (Reported) | 868 | N/A |
The rapid proliferation of this worm underscores the persistent risks inherent in the software supply chain. By targeting widely used libraries like Keyv, the attackers leveraged trust in existing dependencies to automate the injection of hooks into developer workstations. Security teams are advised to audit their package-lock files and review recent dependency updates for any signs of unauthorized modifications or suspicious configuration triggers.
Why It Matters
This incident highlights a dangerous evolution in automated supply chain attacks. By specifically targeting VS Code and Claude Code hooks, attackers are moving beyond simple data theft to intercepting the very tools developers use to build future software. This creates a recursive vulnerability where the development environment itself becomes an attack vector. Organizations must shift from passive dependency monitoring to active, behavioral-based analysis of their build pipelines. Relying solely on version pinning is no longer sufficient when high-utility, trusted packages are compromised at the source level, allowing malicious code to bypass standard CI/CD gatekeepers.
Reader Discussion & Insights