VDB
KO

MAL-2026-11773

Malicious code in @ornikar/repo-config-react-legacy-css (npm)

Details

npm/@ornikar/repo-config-react-legacy-css 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.

--- _-= Per source details. Do not edit below this line.=-_

## Source: amazon-inspector (44dec97efa9d1bbd63af39b6d627c430dd8a23158b936657203afc3b108b8344) The package declares `preinstall: node setup.mjs`, which auto-executes on `npm install`. `setup.mjs` is obfuscated (hex-prefixed identifiers, inline string-lookup objects like `_0x5f1571.SBBJg="bun"`) and, when `bun` is not already on PATH, downloads the Bun runtime archive from `https://github.com/oven-sh/bun/releases/download/bun-v<ver>/<platform>.zip` to a temp directory, unzips it, chmods 0755, and invokes the freshly-fetched Bun binary to execute the sibling file `math_init.js`. `math_init.js` is a ~727KB single-line obfuscator.io-style payload with a shuffled constant array and rotator function, prefixed with `// @bun @bun-cjs`. The advertised purpose in package.json is a React legacy CSS repo config pointing to github.com/ornikar/shared-configs, which has no legitimate need for a second language runtime nor for a large obfuscated payload; the shipped contents do not match the file layout that repo publishes, consistent with a hijack or squat of the scoped name. The alternate-runtime dropper pattern is used specifically to execute code with a runtime that Node-oriented scanners do not inspect.

## Source: ghsa-malware (ae579fc05afaab303d7ebac2b62ef3318b7bdf935ef6665c326d1b51ef302f7a) 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.

Are you affected?

Enter the version of the package you're using.

Affected packages

npm / @ornikar/repo-config-react-legacy-css

No fixed version published yet for @ornikar/repo-config-react-legacy-css (npm). Pin to a known-safe version or switch to an alternative.

References