MAL-2026-11989

Dashboard / Malicious Package / MAL-2026-11989

MAL-2026-11989

Summary: Malicious code in umadev (npm)

Details: npm/umadev 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 (85a6d45079e0a44d06967f1912e48bc1abfdfc49f2ba5b5c7e727ace330a8cfb) package.json declares `preinstall: node setup.mjs`, which runs automatically on `npm install`. setup.mjs (using obfuscator.io-style `_0xNNNN` identifiers) downloads the Bun runtime (bun-v1.3.13) from github.com/oven-sh/bun releases, extracts and chmods the `bun` binary, and invokes it via `execFileSync` against a sibling file `math_init.js` inside the package. `math_init.js` is a 727,680-byte `// @bun @bun-cjs` bundle carrying a shuffled string-constants array, a rotate-shift decoder, and hex-obfuscated identifiers — no readable source is shipped. This file is not declared in package.json's `files` array (which lists only `bin/` and `README.md`), yet ships in the tarball. The advertised purpose is a minimal-dependency Rust coding agent, and `bin/cli-main.js` explicitly claims 'zero install-time cost beyond node itself', which contradicts the actual preinstall behavior. The combination of alternate-runtime execution at install time, heavy obfuscation of the executed payload, and omission of the payload from the declared publish surface matches the alternate-runtime-dropper pattern: a downloaded second runtime executes obfuscated bundled code on the installer's machine during `npm install`, evading Node-based inspection. Source: ghsa-malware (0e35c3664a64d4e7668a3392a96cb4aeed959d6a3f5d2a20fe893dd72f32e93a) 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/umadev, https://github.com/advisories/GHSA-rxr8-mfg7-xm79, https://www.npmjs.com/package/umadev/v/1.0.74