MAL-2026-20110: Malicious code in canvas_webgl_minimal (npm)
Malicious package. A preinstall (and preupdate) script runs node index.js, which reads /etc/passwd (and attempts the Windows SAM hive and C:\Users), lists the current working directory, runs id/whoami, collects the user name, home directory, UID/GID and OS release, and posts it all to a hardcoded Discord webhook (1471187072869073017). The code labels its messages "Dependency Confusion Executed" and "Bug Bounty Execution", but it runs without consent on any machine that installs it. index.js (sha256 fb8451975ead2a956d3d8092eb2868d1ba9135fb6ef30e75941b1454958f75ae) is shared by canvaswebglminimal and playwright-config; the same webhook is used by google-caja-bower (MAL-2026-10186). Published 2026-02-23 and unpublished from npm on 2026-02-24.
Affected Software
Event History
Frequently Asked Questions
What systems are exposed if this package was installed?
Any machine that installs the package is exposed because its preinstall and preupdate lifecycle scripts execute node index.js automatically. The script targets both Unix-like and Windows environments, attempting to read /etc/passwd, the Windows SAM hive, and C:\Users.
What information may have been sent to the attacker?
The script collects the current working-directory listing, output from id or whoami, user name, home directory, UID/GID, OS release, and attempts to collect account-file data. It posts collected data to the hardcoded Discord webhook 1471187072869073017.
How can I determine whether this malicious code executed in my environment?
Review npm install and update activity for canvas_webgl_minimal, especially during the period it was published on npm, 2026-02-23 through 2026-02-24. Investigate process or network telemetry for node index.js executions and outbound requests to Discord; the known file hash for index.js is fb8451975ead2a956d3d8092eb2868d1ba9135fb6ef30e75941b1454958f75ae.
Is removing the package enough if it was already installed?
Removing the package stops future execution through its lifecycle scripts, but it does not undo data that may already have been sent to the webhook. Treat any credentials or sensitive system information accessible to the installing user as potentially exposed and investigate affected hosts.