SHAI-HULUD: WHOEVER CONTROLS YOUR PACKAGE REGISTRY CONTROLS YOUR PIPELINE

Summary from the TLDR InfoSec newsletter

The npm worm lineage has evolved to a point where standard supply chain provenance mechanisms can no longer guarantee safety. During the August 2026 ChainDrop campaign, threat actors compromised over 400 packages in under four hours by hijacking a maintainer's legitimate signed release pipeline. The attackers utilized authorized infrastructure, so every poisoned package version successfully carried a perfectly valid SLSA attestation. To further evade traditional domain blocklists, the campaign hosted its command and control operations within an Ethereum smart contract. This attack builds upon the previous Shai-Hulud worms, which have recently pivoted to targeting authentication tokens for AI development tools like Claude, Codex, Cursor, and Gemini. Security researchers warn that these identical mechanics could easily compromise infrastructure-as-code pipelines, proving that current attestation models verify origin rather than actual code legitimacy. To defend against these pipeline hijackings, organizations must enforce strict version pinning, utilize curated registries, implement OIDC-scoped credentials, and apply aggressive network egress restrictions.