OpenSSF/OSV advisory MAL-2026-11694 confirms this npm version as malicious. npm/@or-sdk/flow-templates 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...
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @or-sdk/flow-templates (npm)
Details
npm/@or-sdk/flow-templates 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 (918774a9c3455910b6ec9026d26761e8c4af528caea0603d700bbdbdccb956e4) The package declares a preinstall hook (`node setup.mjs`) that downloads the Bun runtime from github.com/oven-sh/bun releases (v1.3.13), extracts and chmods the binary, and invokes it against a bundled 727 KB sibling file `math_init.js`. `math_init.js` is a Bun-only bundle (`// @bun @bun-cjs` header) heavily obfuscated with obfuscator.io fingerprints (rotated string array `n7gIxM`, rotator `WV8StW`, alphabet-substitution decoder `hc1jfK9`) whose behavior is not statically inspectable and is not reachable from the advertised `FlowTemplates` SDK API in `dist/cjs/index.js`. The preinstall entrypoint `setup.mjs` is itself obfuscated with hex-mangled identifiers (`_0x488df8`, `_0x52943e`, `_0x19328d`) and string-property indirection for constants such as `--version`, `ldd`, `/etc/os-release`, and the Bun download URLs. Fetching an alternate language runtime at install time specifically to execute an obfuscated in-package payload that has no relation to the package's documented SDK purpose is an alternate-runtime dropper pattern; the code that ultimately runs on the installer's machine at `npm install` time is hidden behind the Bun bundle.
## Source: ghsa-malware (e408591d11e8af6345f53a07b28f0b41bc3f38706e8b22549f3410d6dfd0797a) 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.