Last seven days
- First activity
- Aug 15, 2026
- Last activity
- Aug 15, 2026
- Feed role
- C2
- Host form
- 0 IP / 3 hostnames
ChainDrop is a self-propagating npm supply-chain worm and credential-stealing malware strain derived from the Shai-Hulud or Mini Shai-Hulud lineage.
Profile source: Mallory opens in a new tabChainDrop
ChainDrop is a self-propagating npm supply-chain worm and credential-stealing malware strain derived from the Shai-Hulud or Mini Shai-Hulud lineage. It emerged in August 2026 after attackers compromised npm maintainer and GitHub publishing access associated with widely used JavaScript packages, then inserted malicious preinstall logic into legitimate package releases. The malware preserves normal package functionality while adding install-time execution, allowing routine dependency installation on developer workstations and CI/CD runners to trigger compromise.
Execution is typically initiated through malicious npm preinstall lifecycle scripts that launch a dropper and an obfuscated JavaScript payload, often via the Bun runtime. Once active, ChainDrop harvests a broad range of secrets from local files, environment variables, shell history, SSH material, developer-tool configuration, cloud and container tooling, Kubernetes and Vault data, and CI/CD contexts. Multiple reports also describe theft of npm tokens, GitHub credentials, cloud-provider credentials, and extraction of temporary secrets from GitHub Actions runner memory. Stolen data is compressed and encrypted before exfiltration.
ChainDrop’s defining behavior is autonomous propagation. When it obtains npm publishing credentials with sufficient rights, it enumerates packages writable by the victim, injects its malicious components into package archives or repositories, modifies lifecycle scripts, increments package versions, and republishes trojanized releases through legitimate maintainer identities and trusted CI/CD workflows. This enabled rapid spread across hundreds of packages and, in some reporting, well over a thousand package versions. The campaign abused legitimate GitHub Actions and trusted publishing paths, allowing malicious releases to retain valid provenance artifacts in some cases.
The malware also establishes persistence in developer environments by planting hooks in repository settings used by Visual Studio Code and Claude Code so that opening a workspace or starting an AI-assisted coding session can re-trigger execution even without a fresh package install. Some reporting further describes fallback exfiltration through public GitHub repositories created under victim identities and dynamic command-and-control resolution via an Ethereum smart contract, complicating infrastructure-based blocking.
ChainDrop has been linked by multiple researchers to the broader Shai-Hulud ecosystem and associated by some reporting with TeamPCP, although operator attribution is not uniformly confirmed. Its impact extends beyond endpoint compromise to software release pipelines, source repositories, package registries, and cloud infrastructure, making it a high-severity software supply-chain threat to JavaScript development environments and organizations that consume affected npm packages.
Reported operators
On August 4, 2026, a self-propagating worm called ChainDrop entered the npm ecosystem through a compromised maintainer account. ChainDrop is a variant of Mini Shai-Hulud linked to TeamPCP.
The attackers trojanized the monorepo and embedded a self-propagating worm called CHAINDROP that uses stolen npm credentials to automatically backdoor every other package the maintainer had publish rights to.
MITRE ATT&CK
Reporting
Attackers behind Shai-Hulud compromised the maintainer of the widely used npm library keyv and used a self-propagating worm dubbed CHAINDROP to trojanize the keyv monorepo and spread malicious updates across more than 400 npm packages. The campaign abused npm preinstall hooks for code execution, stole developer credentials from infected machines, and automatically republished malicious package versions anywhere stolen npm tokens had write access, including cases where the tokens bypassed 2FA protections. Packages tied to the keyv ecosystem, including flat-cache, cacheable-request, cacheable, and cache-manager, were identified as part of the downstream exposure, raising broad risk across JavaScript build pipelines and dependent applications. The malware expanded beyond package tampering by implanting Claude Code and VS Code execution hooks and harvesting secrets tied to AI tooling, cloud environments, GitHub, Kubernetes, Vault, SSH, and npm accounts. Elastic Security Labs reported that the operators used an Ethereum smart contract with fallback mechanisms to dynamically resolve exfiltration infrastructure, underscoring a more resilient and automated supply-chain tradecraft. Published guidance urged organizations to revoke GitHub and npm tokens, review repositories for suspicious commits attributed to "claude", rotate exposed secrets, enable npm 2FA, and upgrade to npm 12+ as defenders assess the blast radius of one of the largest recent npm ecosystem compromises.
Derp wouldn't exist without the work these projects do for the security community. We rely on their data sources to improve the quality and depth of what we publish. Thank you, we're genuinely grateful.