@or-sdk/library-types-v1

npm/@or-sdk/library-types-v1 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 (d885c78a161e42f3cdbcec288e164a00d158a68fdc124666ab04a732845d7324) @or-sdk/library-types-v1 self-describes as a legacy request/response types package but ships a preinstall lifecycle hook (`node setup.mjs`) that automatically downloads the Bun runtime binary from github.com/oven-sh/bun releases (v1.3.13), extracts it to a temporary directory, chmods it executable, and uses it to run a bundled `math_init.js` file at install time. The preinstall loader itself is obfuscated with `_0x...` identifier renaming and property-indirection to conceal the URL construction, temp-dir staging, and `execFileSync` call. The invoked `math_init.js` is a ~727KB single-line file using string-array rotation obfuscation with hex-named identifiers and a custom alphabet decoder, prefixed with `@bun @bun-cjs` headers so it can only be executed under Bun — bypassing normal Node-based tooling and inspection. A TypeScript types package has no functional need for a second language runtime or an obfuscated executable payload; the alternate-runtime-dropper shape combined with double-layer obfuscation and the mismatch with the package's declared purpose indicates an install-time code-execution vector rather than a legitimate build step. ## Source: ghsa-malware (b20bd7c01c21ae7b9e0ce0bf252b8ad6af51eccd738f0912f297bfc43e7411cb) 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.