MAL-2026-11614

npm/@onereach/orest-cli 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 (1cefc9e09c45ba5abb0aa14c55f4f36e3d82fd746d885de20c225a3b340de5b3)

The package's preinstall hook (node setup.mjs) downloads the Bun runtime from the oven-sh/bun GitHub releases, marks it executable, and invokes it against math_init.js — a 727KB single-line Bun-CJS bundle shipped in the tarball that carries obfuscator.io fingerprints (rotated string-array decoder WV8StW/n7gIxM, hex-mangled _0xNNNN identifiers, cover names MmgoCP, etDiOOB). The payload's contents cannot be resolved without executing its decoder, embedded strings include hostname-shaped tokens that only materialize at runtime, and its purpose has no relationship to the package's advertised OREST CLI functionality. Naming the payload math_init.js and shadowing it behind short cover variables (V, E, mu) in setup.mjs disguises the dropper as build-time initialization. lib/orest-micro/commands/publish/ssoAuth.js additionally combines child_process with hardcoded outbound POST/GET calls. The Bun binary itself comes from a legitimate pinned URL, but the code it runs on npm install is attacker-authored, obfuscated, and executed on the installer's host with the installer's privileges.

Source: ghsa-malware (009ce0597f2062ba8e25da996099f2f67f168de03423dbe2922c4bfbbbeca113)

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.