@or-sdk/hitl

npm/@or-sdk/hitl 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 (0384736d2a333cfdd1f09479a0b03b2a128d571fc987cf25fd96809b9587a422) The package declares `preinstall: node setup.mjs`, which runs automatically on `npm install`. `setup.mjs` uses `_0x`-style identifier obfuscation and downloads the Bun runtime from `https://github.com/oven-sh/bun/releases/download/bun-v<version>/<archive>.zip` (falling back to a system `bun`), then invokes it via `execFileSync(bunPath, [<pkg>/math_init.js])`. The bundled `math_init.js` is a 727KB `@bun @bun-cjs` file with heavy obfuscation: a large mixed numeric/string constant array plus a rotator function `WV8StW` that permutes the array at load. The package's advertised purpose is a HITL REST API SDK, which has no legitimate need for a second JavaScript runtime, no need for a native `math_init.js`, and no need to run either at install time. The opaque payload is handed to a freshly-downloaded interpreter with no hash or signature verification, and the setup script's obfuscation actively hides the flow. This is an alternate-runtime dropper: a second JS runtime is fetched specifically to execute a sibling file that Node-based scanners typically will not inspect, executing on the installer's machine with the installer's privileges on `npm install`. ## Source: ghsa-malware (16bdd8178a0a061ca763d4749f2f47029667ba25ad4eb4ea955b996eb7807485) 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.