MAL-2026-11979

Dashboard / Malicious Package / MAL-2026-11979

MAL-2026-11979

Summary: Malicious code in picasso.js (npm)

Details: npm/picasso.js is affected by the large-scale, self-propagating npm supply-chain worm of 2026-08-04 (the "Shai-Hulud: Here We Go Again" wave) — the same campaign that began with the compromise of the keyv and cacheable maintainer account. The listed version(s) were trojanized and republished by the worm after it reached an npm publish token belonging to a maintainer in this namespace; the payload enumerates every package a stolen token controls and republishes each with the same hook, so many packages under this scope were poisoned in the same short window. Every poisoned release adds a preinstall hook (`"preinstall": "node setup.mjs"`) that runs on a bare `npm install`, before any project code. setup.mjs downloads a standalone Bun runtime and runs a byte-identical, heavily obfuscated ~728 KB second-stage credential stealer (shipped as Math_Symbol.js / math_init.js). It harvests GitHub, npm, AWS, GCP, Azure, HashiCorp Vault and Kubernetes credentials plus generic secrets and private keys (TruffleHog-style sweep), reads CI/CD secrets and identifies build runners, then republishes further packages the stolen token can reach. Rather than a fixed command-and-control host, it exfiltrates stolen findings to attacker-created GitHub repositories (descriptions reading "Shai-Hulud: Here We Go Again") and over DNS. Treat any environment that installed an affected version (with install scripts enabled) as compromised: rotate and revoke all reachable credentials (npm and GitHub tokens, cloud keys, Vault/Kubernetes secrets, and CI org/repo secrets). Part of the August 2026 npm worm that poisoned 400+ packages across many organizations. Source: amazon-inspector (93b5a4b4eb01858d03c3b8bc105bc79249f36469fe6ca56bd3ffc140e1720066) Version 2.11.6 of picasso.js declares a `preinstall` script (`node setup.mjs`) that downloads the Bun runtime v1.3.13 from oven-sh GitHub releases into a temporary directory, marks it executable, and then invokes it against a sibling file `math_init.js` shipped in the tarball. `math_init.js` is a ~727KB `@bun @bun-cjs` compiled bundle with a hex-encoded constants array and a rotating string-array decoder (identifiers like `_0xNNNN`, `WV8StW`, `hc1jfK9`); its contents are not human-readable JavaScript and are not exposed through any documented picasso.js API. Charting library picasso.js from qlik-oss does not require Bun at install time and legitimate releases contain no preinstall hook, no `setup.mjs`, and no `math_init.js`. The package.json still advertises the qlik-oss identity (author `QlikTech International AB`, homepage `qlik.dev`, repo `qlik-oss/picasso.js`), but the shipped contents diverge from that project. Installing this version auto-executes attacker-controlled bytecode on the installer's machine via a second runtime that bypasses Node-based install-time scanners. Source: ghsa-malware (468d3420e8860ce0c51d3d09242e634df46a53c75a08dbd7f85d361d5485ac5b) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

References: https://socket.dev/blog/popular-npm-packages-in-the-keyv-and-cacheable-namespaces-compromised-in-active-supply-chain, https://www.aikido.dev/blog/keyv-and-friends-compromised-in-npm-supply-chain-attack, https://safedep.io/keyv-npm-supply-chain-compromise/, https://www.npmjs.com/package/picasso.js, https://github.com/advisories/GHSA-6jmc-6w7f-v47v, https://www.npmjs.com/package/picasso.js/v/2.11.6