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

@ornikar/eslint-config-react is a confirmed malicious npm package (MAL-2026-11750) that steals credentials and exfiltrates sensitive data (malicious versions 24.0.1, 24.0.2, 24.0.3…). Do not install it — remove it immediately and rotate any exposed credentials.

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

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

What this malware does

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

This release of @ornikar/eslint-config-react declares scripts.preinstall = "node setup.mjs", which fires automatically on npm install. setup.mjs is obfuscated (obfuscator.io-style _0xNNNN identifiers, per-function string-property lookup tables) and downloads the Bun runtime from https://github.com/oven-sh/bun/releases/download/bun-v<version>/...zip, extracts it, then execFileSyncs the downloaded Bun binary against a sibling file math_init.js. math_init.js is a ~727KB @bun @bun-cjs bundle with a shuffled string/number array and a custom character-substitution decoder (hc1jfK9) — its real behavior is hidden from static inspection and it is executed under an alternate JavaScript runtime that Node-focused install-time scanners do not observe. The declared purpose of the package is a plain ESLint flat-config (main: index.js); fetching a second JavaScript runtime and executing a 700KB obfuscated bundle at install time has no relationship to that purpose. The tarball composition (ESLint-config metadata alongside an obfuscated loader, an obfuscated payload, and a preinstall lifecycle hook that wires them together) is consistent with a maintainer-account compromise or malicious release into the @ornikar scope rather than a legitimate publish.

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
24.0.124.0.224.0.324.0.424.0.524.0.624.0.724.0.824.0.924.0.1024.0.11

Indicators of compromise (SHA-256)

83c979ca0decb09b8e2f82a39c7c02c58bdfff61ef3c936d37ba9c27bf686219
c43fe18efd20c87dd0bebf2bd584566c90a5bd3b3a5b8f470884b762be25bb7a
035497cad10bdab9bcd2fc10536a3b39d63ef9546738769a9b4850c4c7f6b6d4
16ca15fbf1ec37e708f5706fe84ca7d9d31be26d06ccee82b300f17fb2e4a765
210aa9f54f2ba8d482cf4fcad0714269135a75b480098e26f286089603b3b39b
82d747d83531d22b9815c38918bc92fa50a6bd9e6c2343528660803097b92147
9a237845714be19f890b7b1ce4c25523a0189faefaeb8369544b921aa81a54ca
9ab6036bd7c661b86f7e7865f6c984666bb7c59130f8aa03483da7d67177ffff
4d7f7ef1c9fb5e6565361ece418df599430a9adacffe0719a67c5b18321e2d30
4dad56c3080f81dbfc2e573c133124bace20b4eca25ebed3437697f859dfcdd0
5e252dbbab7b0adf016050429a19be3687d80a9ba38c7ce3c47c339a0ea7797f
aed53a6b37f0e429faa54bcfaa3c650d779a25cbe9294ee92ce8587389d770ff

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/eslint-config-react (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/eslint-config-react across your stack and pipelines.

  2. If you installed it — respond

    @ornikar/eslint-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/eslint-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/eslint-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/eslint-config-react on npm has been identified as a malicious package (versions 24.0.1, 24.0.2, 24.0.3, 24.0.4, 24.0.5, 24.0.6, 24.0.7, 24.0.8, and 3 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-h957-h79m-9cv6IN-MAL-2026-011396IN-MAL-2026-011864IN-MAL-2026-011866IN-MAL-2026-011605IN-MAL-2026-011867IN-MAL-2026-011607IN-MAL-2026-011561IN-MAL-2026-011669IN-MAL-2026-011557IN-MAL-2026-011670IN-MAL-2026-011758

References

Credits

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

Detect & block this

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