New 'Worm' Actively Attacking Software Supply Chains
A new npm worm, comprised of at least 19 packages, is actively attacking software supply chains. The malware is reportedly capable of stealing secrets, injecting malicious workflows, and poisoning AI toolchains. The attack highlights increasing cybersecurity risks in tech-dependent retail operations.
- This new worm utilizes a "time-bomb" technique, remaining dormant for 48 hours after installation to evade detection before it begins to steal API keys, secrets, and tokens. - The 19 malicious packages identified include names like `claud-code`, `crypto-locale`, `hardhta`, and `node-native-bridge`, and the worm spreads by tampering with a developer's Git configurations to compromise new projects automatically. - A key feature of this attack is its focus on AI development tools, where it injects malicious configurations to steal Large Language Model (LLM) API keys and SSH keys from AI coding agents and IDEs like Claude Code, Cursor, and VS Code. - This incident is part of a larger trend of increasingly sophisticated software supply chain attacks, with a predicted 45% of organizations worldwide expected to experience such an attack by 2025. - The use of open-source repositories like npm as an attack vector is a known and growing threat; in 2023, there was a 28% increase in malicious packages uploaded to these repositories compared to the previous year. - Another concurrent campaign targeting developers involves the North Korean Lazarus Group, which has been active since at least May 2025 and uses fake recruiter personas on platforms like LinkedIn to trick developers into using malicious npm and PyPI packages. - The potential business impact of such supply chain attacks is significant, as demonstrated by incidents at other major companies where similar breaches have led to operational disruptions, reputational damage, and financial losses. - In response to previous worm attacks like "Shai-Hulud" in 2025, npm implemented a major authentication overhaul in December 2025, yet vulnerabilities remain as multi-factor authentication for publishing packages is still optional.
