@ornikar/webpack-config@12.0.12

npm/@ornikar/webpack-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. --- ## Source: amazon-inspector (a0f8a697dae174cc1f1e0e76112683bc22e594972a3698714af850a8a495d91c) The package advertises itself as a webpack configuration helper but ships no webpack code: package.json's declared main `index.js` is absent from the tarball, README is a 50-byte stub, and the tarball's substantive contents are an install-time dropper. package.json declares `scripts.preinstall = "node setup.mjs"`, which fires automatically on `npm install`. `setup.mjs` is itself obfuscated (`_0xNNNN` identifiers, string-map indirection), downloads the Bun runtime from `github.com/oven-sh/bun/releases/download/bun-v<ver>/<arch>.zip`, extracts the `bun` binary to a temp directory, chmods it executable, and then invokes it via `execFileSync` to run the bundled 727KB `math_init.js`. `math_init.js` is a single-line string-array-VM-obfuscated bundle (`// @bun @bun-cjs` prefix, shuffled constant array `n7gIxM`, rotation function `WV8StW`, custom-alphabet decoder) whose behavior is opaque to Node-based supply-chain scanners because execution is routed through Bun. The purpose is undocumented and unrelated to webpack configuration. The identity/contents mismatch (webpack-config name, no webpack code, dominant content is an obfuscated Bun-driven payload) is consistent with a maintainer-account or publish-token compromise republishing the package name with an attacker payload. ## Source: ghsa-malware (a0b158187367b485679f3207760041ce850fa288f1639c0e2c3fc49c8952720d) 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.