MAL-2026-11953

npm/@umacloud/cli-darwin-arm64 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 MathSymbol.js / mathinit.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.

-= Per source details. Do not edit below this line.=-

Source: amazon-inspector (368a2fdb65160a548b9f973b5ecbfdcc11f861e791cf8a1fbc039820392eb48b)

The package's preinstall hook runs setup.mjs, which downloads the Bun runtime from github.com/oven-sh/bun (pinned v1.3.13) into a temp directory, extracts it, chmods +x, and uses it to execFileSync a sibling bundle math_init.js on npm install. setup.mjs is written with javascript-obfuscator-style hex identifiers (_0x488df8, _0x52943e, _0x19328d) and per-function string-lookup objects. The package already ships a self-contained compiled binary at bin/umadev, so a second runtime fetch at preinstall time to execute additional bundled code is out of profile for the declared purpose (a platform-specific CLI binary distribution). The combination of an obfuscated lifecycle script plus an alternate-runtime execution of a bundled sibling file gives the maintainer a channel to run arbitrary code on the installer's machine at npm install time, and hides what that code does from review.

Source: ghsa-malware (e364de42d2a7d5ed869d2c9c53c2b7aeb83661d9b7816486e6d6efc9501ebc53)

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.