@ornikar/postcss-confignpm

npm/@ornikar/postcss-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 a preinstall hook 'node setup.mjs'. setup.mjs is obfuscated (hex-mangled identifiers) and, at npm install time, downloads the Bun runtime archive from github.com/oven-sh/bun releases (v1.3.13), writes the bun binary to a temp directory, chmods it executable (mode 0755), and then invokes bun to execute the sibling file math_init.js. math_init.js is a 727KB single-line Bun-compiled module ('// @bun @bun-cjs' header) with a numeric string-array lookup table shuffled at load and hex-mangled identifiers (MmgoCP, etDiOOB, JqTtnbZ, bc3Kak,...). The advertised purpose of the package is a small PostCSS configuration exporting four plugin factories, which has no need for the Bun runtime or an opaque 727KB compiled bundle. The alternate-runtime-dropper shape — a lifecycle hook fetching a language runtime and using it to execute a bundled sibling that Node-based scanners cannot introspect — combined with heavy obfuscation of both the loader and the payload matches the install-time remote-execution attack pattern. Installing this version causes attacker-controlled bytes to execute on the installer's host at npm install time.

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.