Researchers: ChainDrop, a Shai-Hulud-based worm, has compromised 1,300+ npm packages, like Keyv, Cacheable, and flat-cache, with a combined 2B monthly downloads
Self-propagating malware named ‘ChainDrop’ has compromised more than 1,300 packages with a combined 2 billion monthly downloads on the Node Package Manager (npm) registry.
BleepingComputerBill Toulas
Context & Ripple Effects
ChainDrop extends the Shai-Hulud npm campaign: related coverage previously identified more than 600 malicious package versions, largely in the @antv ecosystem. The new report indicates a broader, self-propagating phase rather than an isolated package compromise.
Maintainers and users of the more than 1,300 affected packages must identify whether compromised releases entered their builds, remove or replace them, and rotate any credentials potentially exposed during installation or execution.
The named package ecosystems face immediate trust and release-management pressure as downstream projects scrutinize versions and lockfiles rather than treating download volume as a safety signal.
Second-order effects
Application teams and security vendors will expand dependency inventories and CI checks to trace transitive npm exposure, increasing the operational cost of using broadly shared packages.
Other npm maintainers may tighten publishing controls and review release provenance after the earlier Shai-Hulud wave of 600-plus malicious versions showed how a campaign can spread across an ecosystem.
Third-order effects
If self-propagating package compromises persist, npm security will shift further from assessing individual libraries to continuously verifying the integrity of the dependency graph and the identities behind releases.
The incident reinforces a market in which maintainers of foundational utilities carry disproportionate ecosystem risk, likely increasing demand for stronger registry safeguards and provenance tooling; the extent of durable adoption remains uncertain.
The trend: ChainDrop is part of the shift from one-off malicious packages toward scalable, dependency-graph attacks that exploit the reuse at the core of modern software distribution.
This morning, several high-profile npm packages — including keyv, file-entry-cache, and flat-cache — were compromised. The malicious payload appears to have the ability to spread to adjacent npm packages. Datadog Security Labs has identified the worm and is analyzing the situatio…
🚨 Update: Watching this npm worm propagate in real time, we're now tracking 2,234 affected package artifacts across 444 unique packages, and it's still spreading. Average detection time: 5 min and 18 seconds after publication. Our campaign page includes all packages/versions.
‼️ The popular npm package keyv is being actively compromised (127 million weekly downloads). The attacker is still pushing malware across packages right now. Developing story. [image]
Between cacheable and keyv, we're now seeing active community spread. At least two developers with live tokens have been hit and have published a dozen compromised packages.
🚨 Active npm supply chain attack: keyv @ 6.0.0 and 13 other packages have been compromised. keyv alone gets 154M weekly downloads. The worm steals cloud and CI credentials, then uses stolen npm tokens to publish trojanized versions of more packages. [image]
i think we are entering a post-package era. 95%+ of packages can very easily be rebuilt at this point. and when you care more about bad actors than the risk of a bug, it makes sense.
npm is rotating write-scoped npm Granular Access Tokens that bypass 2FA as a precaution following a now-contained security incident. This doesn't affect GitHub personal access tokens. Maintainers should upgrade the npm CLI to v12+ and consider Trusted Publishing.