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/prettier-confignpm

@ornikar/prettier-config is a confirmed malicious npm package (MAL-2026-11766) that steals credentials and exfiltrates sensitive data (malicious versions 9.0.3, 9.0.4, 9.0.5…). Do not install it — remove it immediately and rotate any exposed credentials.

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

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

What this malware does

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

This version of @ornikar/prettier-config declares a preinstall hook node setup.mjs that fires automatically on npm install. setup.mjs downloads the Bun runtime from github.com/oven-sh/bun releases (arch-specific zip), extracts it to a temp directory, chmods it executable, and invokes it via execFileSync to run a bundled sibling file math_init.js. math_init.js is a ~727KB single-line obfuscator.io-style payload (shuffled string array with a rotating shift routine, hex-mangled identifiers, multi-thousand-entry encoded constants table) whose filename has no relationship to the package's stated purpose. A Prettier config package's declared functionality is delivered entirely by a ~20-line index.js exporting a config object; there is no legitimate reason to fetch a second language runtime and execute an obfuscated blob under it at install time. The alternate-runtime execution path bypasses tooling that only inspects Node-resolved code. Prior legitimate versions of this package under the same @ornikar scope ship only the config file and declare no install hooks, so 9.0.6 introduces both the preinstall hook and the two undeclared payload files (setup.mjs, math_init.js).

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

9 flagged
9.0.39.0.49.0.59.0.69.0.79.0.89.0.99.0.109.0.11

Indicators of compromise (SHA-256)

458f494d8a6a3871b1a2bf175349bc345cc3d009ecf08b6a2bce4e34ae7ea9ed
ce569324ce4ff2b4684f1f473eaf2432d3716973b2e35d713e579ce9dcfe3045
00b022a82c891baac27ba761654183cdbc964385ccd10e2dbee8cdaa10887d37
047bb802dd6b7f3e17acdbafba698d4fcc06ddde4b34bb08a6027ca0a62825f0
2d66a5b15be487fd4bb8e04e05ac98ac5ae79f1d304f701a2b9d2009010b22f7
424e9082e1c42a20a03f2817184d19dba1caf6154757576a3ddd7cce226fb886
45e7520857c1d3bc86e60d54aa0114717650034dbc72687af53eb6af95078f87
4fb7a25412dfc103fd6aea7acd63399a780eec1549ee4a7cd6b0007c3d8c33e7
895ed49b94353188ce5583efaa01063d42702448dec7b1e0c37f4cfc0f4c2c03

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/prettier-config (9 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ornikar/prettier-config across your stack and pipelines.

  2. If you installed it — respond

    @ornikar/prettier-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/prettier-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/prettier-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/prettier-config on npm has been identified as a malicious package (versions 9.0.3, 9.0.4, 9.0.5, 9.0.6, 9.0.7, 9.0.8, 9.0.9, 9.0.10, and 1 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-g5xj-fh96-3782IN-MAL-2026-011735IN-MAL-2026-011540IN-MAL-2026-011734IN-MAL-2026-011612IN-MAL-2026-011609IN-MAL-2026-011611IN-MAL-2026-011738IN-MAL-2026-011577

References

Credits

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

Detect & block this

O3 blocks @ornikar/prettier-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/prettier-config (npm) malicious package — MAL-2026-11766 | O3 Security