On August 4, 2026, the ChainDrop worm, a variant of Mini Shai-Hulud associated with TeamPCP, compromised the npm ecosystem by abusing a maintainer account of the keyv ecosystem. The attacker injected malicious code into GitHub repositories and leveraged legitimate CI/CD pipelines to publish poisoned npm packages carrying valid SLSA Build Level 3 provenance attestations, making the malicious packages indistinguishable from legitimate releases. ChainDrop rapidly propagated to over 400 npm packages within four hours by stealing npm tokens and republishing infected versions. The worm's command and control infrastructure is implemented via Ethereum smart contracts, allowing domain rotation without altering the deployed malware. It includes destructive functionality that wipes victim home directories if tokens are revoked and maintains persistence through IDE and AI-agent configuration files. The malware harvests credentials from npm, GitHub, AWS, Azure, GCP, Kubernetes, HashiCorp Vault, and other services, exfiltrating data through GitHub repositories and EtherHiding techniques.

ChainDrop compromises the npm supply chain by injecting malicious code into widely used packages, enabling rapid propagation across hundreds of packages. It steals authentication tokens to republish infected packages, undermining trust in the software supply chain. The worm's destructive payload can wipe victim home directories, causing data loss. It also harvests sensitive credentials from multiple cloud and development platforms, risking extensive data exfiltration and further compromise of cloud and infrastructure environments. The use of Ethereum smart contracts for C2 infrastructure complicates detection and takedown efforts due to domain rotation capabilities. Persistence through IDE and AI-agent configuration files increases the difficulty of complete removal.

No official patch or fix is indicated in the available data. Organizations should immediately audit and revoke compromised npm tokens and credentials associated with affected maintainer accounts. Review and harden CI/CD pipeline security to prevent unauthorized package publishing. Monitor for indicators of compromise such as the listed malicious domains and hashes. Investigate and clean infected development environments, including IDE and AI-agent configuration files, to remove persistence mechanisms. Employ credential rotation and enhanced monitoring on cloud and development platforms to detect and respond to potential exfiltration attempts. Consult the referenced vendor advisory and threat intelligence sources for ongoing updates and guidance.