A significant software supply chain attack has compromised dozens of popular npm packages, deploying a self-propagating worm. Security researchers report that the attack originated from a compromise of the widely used Trivy vulnerability scanner and has since spread autonomously.
The incident, first detected this week, involves a previously undocumented piece of malware dubbed “CanisterWorm.” This malicious code has been found in at least 47 packages within the npm registry, which is a central repository for JavaScript code used by millions of developers worldwide. The worm’s name references its use of an ICP canister, a type of tamperproof smart contract on the Internet Computer blockchain network.
Origin and Method of the Attack
Investigators trace the initial vector to a supply chain attack targeting Trivy, an open-source security scanner maintained by Aqua Security. Threat actors are believed to have tampered with the tool’s infrastructure or codebase. This initial breach then served as a springboard for the secondary, more widespread attack on the npm ecosystem.
The CanisterWorm malware exhibits self-propagating capabilities, meaning it can automatically seek out and infect other packages or systems under certain conditions. This characteristic significantly increases the potential scale and speed of the compromise beyond a single point of failure.
Impact on the Developer Ecosystem
The npm packages affected are used as dependencies in countless web and software applications. When a malicious package is included as a dependency, it can potentially steal sensitive data, deploy backdoors, or cause further damage within an application’s environment. The scale of 47 compromised packages suggests a coordinated and substantial effort to infiltrate the software development supply chain.
Security firms and npm registry maintainers are actively working to identify and remove all infected packages. They have also begun notifying maintainers of affected projects and users who may have downloaded the tainted code.
Response and Mitigation Efforts
Aqua Security, the company behind Trivy, has issued a statement confirming an investigation into the original compromise of their scanner. They are urging all users to ensure they are running the latest, verified version of the Trivy tool. The npm security team has concurrently published a list of identified malicious packages and is recommending developers audit their projects for these dependencies.
Standard advice for developers includes rigorously checking package dependencies, using lockfiles to pin dependency versions, and employing additional security tooling to scan for vulnerabilities and suspicious code. Organizations are advised to review their software bills of materials (SBOMs) for any traces of the listed packages.
Looking Ahead
The full scope of the attack is still being assessed. Security analysts expect the identification of additional compromised packages as the investigation continues. Official timelines from npm and Aqua Security for a complete remediation and a detailed post-mortem analysis are anticipated in the coming days. This event is likely to prompt renewed scrutiny of security practices around open-source software repositories and the tools used to audit them.
Source: Multiple security advisories from npm and Aqua Security
