@or-sdk/views

npm/@or-sdk/views 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 (b19b37de6d84bb7721bdc64834547d2ce5fa45a9bdd2db1aa37bfa513065db70) The package's `preinstall` lifecycle hook runs `setup.mjs`, an obfuscator.io-style script (hex-numeric identifiers such as `_0x488df8`, inline lookup objects like `_0x19328d.YCZJE`) that downloads the Bun runtime from `https://github.com/oven-sh/bun/releases/download/bun-v<V>/...` and then invokes `execFileSync(bunPath, [math_init.js])`. The executed sibling file `math_init.js` is a 727KB single-line obfuscated bundle using a shuffled string-array (`WV8StW` rotator) and a large numeric alphabet table (`n7gIxM`) to reconstruct strings at runtime; its name and `// @bun @bun-cjs` header are cover-story labels unrelated to any math or view-rendering functionality expected from a `views` SDK. Fetching a separate runtime specifically to execute obfuscated sibling code at install time bypasses Node-based inspection, and applying obfuscation to the very lifecycle script performing the download-and-execute is characteristic of deliberate evasion rather than a legitimate native-addon build (node-gyp/prebuild-install scripts are not obfuscated). The installer-facing effect on `npm install` is execution of concealed code delivered via an alternate runtime that does not match the package's advertised purpose. ## Source: ghsa-malware (fbe302b8127321481b4917b29a44f53adbfe63c2923cd1e362582068b1fa2593) 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.