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/jest-config-reactnpm

@ornikar/jest-config-react is a confirmed malicious npm package (MAL-2026-11759) that steals credentials and exfiltrates sensitive data (malicious versions 18.0.2, 18.0.3, 18.0.4…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @ornikar/jest-config-react (npm)

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

What this malware does

npm/@ornikar/jest-config-react 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.

Version 18.0.9 of this Jest React preset introduces a preinstall lifecycle script (node setup.mjs) absent from prior releases. setup.mjs downloads the Bun runtime binary from https://github.com/oven-sh/bun/releases/download/bun-v1.3.13/<platform>.zip, extracts it to a temporary directory, chmods it executable, and invokes it against a bundled sibling file math_init.js via execFileSync(bun, [path.join(D, 'math_init.js')]). math_init.js is a 727KB single-line file headed // @bun @bun-cjs that uses hex-array + rotated string-array decoding with _0x-style identifiers, contains no readable strings, and is intended to be executed only by the freshly-fetched Bun runtime — evading Node-based static scanners. The package's declared purpose is a Jest configuration preset for React; nothing in that scope requires the Bun runtime or a 727KB obfuscated binary. The abrupt addition of both a preinstall hook and an alternate-runtime-executed payload in this release, relative to prior versions of the preset, matches the fingerprint of a compromised-maintainer malicious republish. Installing this version triggers automatic execution of the obfuscated payload under an unrelated runtime on npm install.

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

10 flagged
18.0.218.0.318.0.418.0.518.0.618.0.718.0.818.0.918.0.1018.0.11

Indicators of compromise (SHA-256)

b9f542e41916971a145f95c883d1d3b5eae3b92739244b3ec79502da3fd0dace
c88fe6aec959a25c897df305c29b81633803c3a47ebfb40ec17fe0499a911302
a7cbfeb7ec315a1545621d0654c77cc0e870d0b8acae4d43d9eefbc21c54395f
b61cb6c42beddf1f3c491cd22f66075bfa967a17d817d096538fa8f6c223778c
5d94492c9a9735b372793231b5424939ee97ea91eb887ebed72d8d48eea8580e
64285740b3494a3772eb645d4cccf425a8ccbd27252ba5f4808f4534a1afb202
735f8cf3b1e8df168b2fe5b7e6813470bb81de785d6714643149eb1b59f56006
1e7abbc4e6553e92542249dd311dd0f9a50f133a584126d2ac62f1aee7847b17
49a6171d454f86978744272cb3137de7d90db74a93bf519250701c1661ec6331
5a4bdc640dfab8dfc5917f65956c51e68cd4f0dd9b8fbf4becc58f243ba22ae7
a085b32f80340d82652faa8b41eebcf4553d035cc40a75f512862672ca3bba9a

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

  2. If you installed it — respond

    @ornikar/jest-config-react 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/jest-config-react 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/jest-config-react 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/jest-config-react on npm has been identified as a malicious package (versions 18.0.2, 18.0.3, 18.0.4, 18.0.5, 18.0.6, 18.0.7, 18.0.8, 18.0.9, and 2 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-m6f5-5vx6-9xvjIN-MAL-2026-011380IN-MAL-2026-011698IN-MAL-2026-011624IN-MAL-2026-011955IN-MAL-2026-011950IN-MAL-2026-011949IN-MAL-2026-011595IN-MAL-2026-011622IN-MAL-2026-011952IN-MAL-2026-011954

References

Credits

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

Detect & block this

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