What happened
StepSecurity published a report on 2026-08-13 (following CloudSEK's full victim-list disclosure) detailing 'ChainDrop', a Shai-Hulud-lineage self-propagating npm worm first identified August 4, 2026. It poisoned 444 packages/2,212 versions within four hours by compromising a keyv maintainer's account and abusing that maintainer's own CI pipelines to auto-publish trojanized releases, harvesting developer, cloud, and AI-tool credentials across 2,186+ organizations.
Why it matters
This supply-chain worm specifically targets developer and CI/CD credentials — including tokens for AI coding agents and model-provider APIs — at a scale (450M+ weekly downloads) that threatens the software supply chain feeding into countless AI-assisted development pipelines; the newly published full victim-exposure list is a material escalation of the prior Shai-Hulud disclosures.
Attack vector
Attackers compromised a maintainer's GitHub account, pushed malicious code directly to main, and triggered the maintainer's own GitHub Actions pipelines to build and auto-publish infected package versions; the worm self-propagates through the dependency graph, harvesting npm tokens, cloud credentials, and CI/CD secrets — including credentials for AI coding tools and model-provider APIs
Affected systems
npm ecosystem packages including keyv, cacheable-request, flat-cache, file-entry-cache and their dependents (CI/CD pipelines, AI coding-agent environments)
Mitigation
Audit for and remove compromised keyv/cacheable/flat-cache/file-entry-cache versions per package advisories; rotate all npm, cloud, and AI-provider credentials in any environment that installed affected versions; review CloudSEK/StepSecurity published victim/exposure list