MAL-2026-11670 Malicious code in @or-sdk/api-tokens-lambda (npm)

Malicious package Published
Package
@or-sdk/api-tokens-lambda
Registry
npm

What is MAL-2026-11670?

MAL-2026-11670 is a malicious package in @or-sdk/api-tokens-lambda, published on 4 Aug 2026.

Official description

npm/@or-sdk/api-tokens-lambda 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.

Package advertises itself as a small AWS Lambda API-tokens wrapper (dist/cjs/ApiTokensLambda.js). package.json declares scripts.preinstall="node setup.mjs". setup.mjs is identifier-obfuscated (obfuscator.io-style _0x… names, property-lookup wrapper objects hiding strings such as "ldd", "–version", "/etc/os-release", "Alpine", "musl", and URL fragments); it downloads a Bun runtime zip from github.com/oven-sh/bun/releases/download/bun-v1.3.13/<platform>.zip, extracts the bun binary to a temp directory, chmods it executable, and execFileSyncs it against the sibling file math_init.js. math_init.js is a 727,680-byte heavily obfuscated bundle using string-array rotation (function WV8StW rotates an n7gIxM constant array; identifiers MmgoCP/etDiOOB/JqTtnbZ). math_init.js is not referenced by dist/cjs/index.js or any other library code; its only invocation path is the Bun binary fetched at preinstall. The package's advertised purpose (AWS Lambda wrapper) does not require Bun, and fetching a second runtime purely to execute an obfuscated bundled payload during npm install both grants install-time code execution on every installer host and evades Node-focused static analysis.

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.

What should I do about MAL-2026-11670?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

Sources

Also known as GHSA-f5mr-g2xw-vv63.

Is MAL-2026-11670 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free