Shai-Hulud is a complex supply-chain malware campaign targeting the npm ecosystem, initially compromising keyv and cacheable libraries among over 400 packages and 1700+ versions. The malware functions as a self-propagating worm that collects sensitive credentials from various environments including local filesystems, CI/CD pipelines, cloud platforms, Kubernetes clusters, and HashiCorp Vault. It exfiltrates this data through dynamic HTTPS endpoints or public GitHub repositories. Using stolen npm tokens, it publishes infected versions of all writable packages, thereby spreading the infection. The campaign further compromises GitHub repositories by injecting execution hooks via VS Code and Claude configuration files and harvesting GitHub Actions secrets through malicious workflows. It also includes targeted attacks on npm trusted publishing processes. The attackers employ resilient command and control mechanisms leveraging Ethereum smart contracts and GitHub commit messages to maintain persistence and control.

The campaign compromises a large number of npm packages, potentially affecting any projects depending on these infected packages. It enables credential theft from multiple environments including local, CI/CD, cloud, Kubernetes, and secret management systems like HashiCorp Vault. The stolen credentials can lead to further compromise of developer environments, cloud infrastructure, and continuous integration pipelines. The malware’s ability to self-propagate and publish infected package versions increases the risk of widespread supply-chain contamination. Injection of execution hooks and harvesting of GitHub Actions secrets further escalate the risk of unauthorized access and lateral movement within development and deployment environments.

No official patch or remediation guidance is provided in the available data. Organizations should monitor official vendor advisories and security research updates for remediation instructions. Immediate mitigation steps include auditing npm package dependencies for compromised versions, revoking and rotating npm tokens and other credentials, reviewing GitHub repository configurations for unauthorized hooks or workflows, and enhancing secret management practices. Since this is a supply-chain attack, organizations should consider implementing strict package integrity verification and supply-chain security best practices. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.