Trivy Scanner Supply Chain Attack Propagates Self‑Spreading CanisterWorm Through 47 npm Packages
What Happened — Threat actors compromised the open‑source Trivy container image scanner and used it as a foothold to inject a previously undocumented, self‑propagating worm—CanisterWorm—into 47 npm packages. The worm leverages Internet Computer (ICP) canisters to auto‑replicate across dependent projects, creating a cascade of malicious code in the JavaScript ecosystem.
Why It Matters for TPRM —
- Supply‑chain compromise of a widely‑used security tool can undermine the trust of downstream vendors and customers.
- The worm’s automatic propagation expands the attack surface across any organization that consumes the infected npm packages.
- Detection is difficult because the malicious code is embedded in legitimate package metadata and executes only in specific runtime conditions.
Who Is Affected — Technology SaaS providers, cloud‑native development platforms, CI/CD pipeline services, and any enterprise that incorporates npm dependencies into production applications.
Recommended Actions —
- Immediately audit all npm dependencies for the 47 compromised packages and any transitive dependencies.
- Verify the integrity of Trivy scanner binaries and update to the latest patched version released by the maintainers.
- Enforce strict SBOM (Software Bill of Materials) validation and provenance checks for third‑party components.
- Communicate with affected vendors to confirm remediation steps and update contractual security clauses.
Technical Notes — Attack vector: third‑party dependency compromise via malicious updates to npm packages. No known CVE; the worm exploits the ability of ICP canisters to execute code without user interaction. Data exfiltration has not been reported, but the worm can introduce backdoors or ransomware payloads. Source: The Hacker News