Self-Propagating Worm Targets npm Packages, Steals Developer Tokens

Cybersecurity researchers have flagged a fresh set of packages that have been compromised by bad actors to deliver a self-propagating worm that spreads through

Cybersecurity

A dangerous supply chain threat has emerged in the JavaScript ecosystem, with cybersecurity researchers uncovering a self-propagating worm that compromises npm packages to steal developer credentials. The malicious campaign, tracked as CanisterSprawl, leverages stolen npm tokens to spread laterally across development environments and project dependencies.

Security teams at Socket and StepSecurity independently detected the worm's activity, identifying how the attack operates within the npm package registry. Once a package becomes compromised, the worm uses hijacked developer tokens to propagate itself to additional packages, creating a cascading infection vector that can compromise multiple projects simultaneously.

The threat derives its name from its use of an Internet Computer Protocol (ICP) canister as an exfiltration channel. This infrastructure choice allows threat actors to siphon stolen authentication credentials while remaining relatively obscured from traditional security monitoring systems. By targeting npm tokens specifically, attackers gain the ability to publish malicious updates under the guise of legitimate maintainers.

This attack demonstrates the continued vulnerability of open-source software supply chains. npm packages are widely integrated into production environments across countless organizations, making the registry an attractive target for sophisticated threat actors. The worm's self-propagating nature amplifies its potential impact, as each newly compromised package can infect others without requiring fresh attacker involvement.

Developers relying on npm should review their token security practices immediately. Rotating credentials, implementing token scoping to limit package access, and monitoring for unauthorized package publications are essential mitigation steps. Organizations should also audit their dependency trees for potentially compromised packages and validate the integrity of recent updates.

The discovery underscores the evolving sophistication of supply chain attacks. Rather than targeting individual packages, modern threats now weaponize the interconnected nature of open-source ecosystems, spreading automatically through trust relationships embedded in development workflows. Security researchers continue tracking CanisterSprawl to assess its full scope and identify all affected packages.

Editorial note: This article represents original analysis and commentary by the TechDailyPulse editorial team.