@ornikar/storybook-confignpm

npm/@ornikar/storybook-config 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.json declares preinstall: node setup.mjs. setup.mjs is obfuscated (obfuscator.io-style _0x... identifiers and string-map indirection) and, at install time, downloads the Bun runtime zip from GitHub releases, extracts it to a temporary directory, chmods it executable, and invokes it against math_init.js — a 727 KB heavily obfuscated JavaScript file bundled adjacent to the loader (rotating string-array decoder WV8StW, numeric/character constant table, hex-obfuscated identifiers). If Bun is already present on the host, it is invoked directly on math_init.js. The package is advertised as a Storybook configuration helper and has no functional need to fetch a language runtime or execute an opaque bundled payload at install time. Running the payload under Bun bypasses Node-based install-time scanners, and the obfuscation of both the loader and the payload prevents inspection of what executes on the installer's machine. This matches the alternate-runtime-dropper shape: the runtime fetch itself is from an official source, but the code that is then executed is the package's own opaque bundled blob whose behavior cannot be audited and whose purpose is inconsistent with the package's stated function.

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.