Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Part of a larger attack: @ornikar published 42 malicious packages. See the full campaign →
Malicious package

@ornikar/stylelint-confignpm

@ornikar/stylelint-config is a confirmed malicious npm package (MAL-2026-11778) that steals credentials and exfiltrates sensitive data (malicious versions 14.0.3, 14.0.4, 14.0.5…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @ornikar/stylelint-config (npm)

MAL-2026-11778
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @ornikar/stylelint-config

What this malware does

npm/@ornikar/stylelint-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.

@ornikar/[email protected] declares a preinstall hook (scripts.preinstall = "node setup.mjs") that runs on npm install. The setup.mjs script is heavily obfuscated (obfuscator.io-style hex-mangled identifiers and string-lookup tables) and downloads the Bun JavaScript runtime from https://github.com/oven-sh/bun/releases/download/bun-v<version>/<platform>.zip, extracts and chmods the binary, then invokes it via execFileSync against a sibling file math_init.js. If bun is already on PATH, it invokes bun math_init.js directly. math_init.js is a 727KB single-line Bun-CJS bundle (// @bun @bun-cjs header, array-shuffle decoder, large numeric/string constant array) — an opaque obfuscated payload executed at install time. The package advertises itself as a stylelint configuration and declares main: index.js, but no index.js is present in the tarball; the only executable content is the preinstall dropper and the obfuscated bundle. A stylelint configuration package has no legitimate reason to fetch an alternate JS runtime and execute a bundled obfuscated payload during install. The combination of install-time alternate-runtime fetch, obfuscation of both the loader and the payload, missing advertised entry point, and package/purpose mismatch is consistent with a hijacked or typosquatted release of the @ornikar/stylelint-config name.

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.

Malicious versions

11 flagged
14.0.314.0.414.0.514.0.614.0.714.0.814.0.914.0.1014.0.1114.0.1214.0.13

Indicators of compromise (SHA-256)

dbbfbcb0e078841f399bcb71594ba12721a9976a2af05ef139c2df93d0d8f84d
b2ddf832981245da751e0d89af699219a5e84db8d3c5791da5176313b4fec5a1
7d9cf994d88b0ca90237c6c69bbf30fc2c9140a072768677f6ae699b79a859d2
8709a8fe4b708219bebbeafb49c97e499131399a2d2a436be3f5d7f4e796f8ff
f57094cff1406d10d5c8cbd8c2173e7e09e30aa139d35c4359436c5ba7c53e96
2e1d032c883da441fd23bde1fbb3f87a11328fa3c3740c3ea5725e3cdd02dd4d
43e9737677a1d9fb68d0f1889b00f8de66b11833340074a4bccccb65d78c9db8
9ef7f92612cf0e14bb92180bc9d14b70e3370b32bfad24eda6470373333a8e22
af6d53d166cef546660259d7888f7a307635484244bb1619ac2322c9e03c5452
b98817070bf2dd6b24f2653e440a1310fe1db6a94a6d23e51ccf096f86f85796
704726ae00a8744ac7ad59738e427ae1e45c4c88fe7a4ccdb468503d0a92180b

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @ornikar/stylelint-config (11 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ornikar/stylelint-config across your stack and pipelines.

  2. If you installed it — respond

    @ornikar/stylelint-config is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If @ornikar/stylelint-config was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks @ornikar/stylelint-config before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @ornikar/stylelint-config on npm has been identified as a malicious package (versions 14.0.3, 14.0.4, 14.0.5, 14.0.6, 14.0.7, 14.0.8, 14.0.9, 14.0.10, and 3 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-r465-crrq-p9mqIN-MAL-2026-011379IN-MAL-2026-011814IN-MAL-2026-011819IN-MAL-2026-011826IN-MAL-2026-011576IN-MAL-2026-011806IN-MAL-2026-011534IN-MAL-2026-011811IN-MAL-2026-011533IN-MAL-2026-011807

References

Credits

  • Aikido Security · finder
  • Amazon Inspector · finder
  • SafeDep · finder
  • Socket Threat Research Team · finder

Detect & block this

O3 blocks @ornikar/stylelint-config-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

@ornikar/stylelint-config (npm) malicious package — MAL-2026-11778 | O3 Security