Which versions of react-next-dom are malicious?

The following npm versions of react-next-dom are flagged malicious: 1.1.7, 17.2.7, 17.2.8. Treat any of these as compromised.

How do I remediate react-next-dom if I installed it?

react-next-dom is a typosquat — you almost certainly intended a legitimately-named package. Remove react-next-dom, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed react-next-dom — how do I know if it already compromised me?

If react-next-dom 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.

Is react-next-dom part of a known attack campaign?

Yes — react-next-dom is associated with the GHSA-99rj-fjph-w44m, RLMA-2026-05258, IN-MAL-2026-009250 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find react-next-dom across my projects, lockfiles, and CI pipelines?

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

Malicious package

react-next-domnpm

react-next-dom is a confirmed malicious npm package (MAL-2026-6825) that typosquats a legitimate package to trick installs (malicious versions 1.1.7, 17.2.7, 17.2.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in react-next-dom (npm)

MAL-2026-6825

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall react-next-dom

What this malware does

react-next-dom masquerades as a React/Next.js ecosystem package but ships a pino-like surface concealing a remote code loader. The main export is a middleware factory that, when invoked, spawns node./lib/caller.js as a detached, stdio-ignored child process (spawn("node", [script,...], { detached: true, stdio: "ignore" }); child.unref()). lib/caller.js then fetches a JavaScript payload from https://jsonkeeper.com/b/D3GLF (using an x-secret-key header), and evaluates the response body in the host Node.js process via new Function.constructor("require", s)(require), retrying up to 5 times. Additional payload URLs (https://jsonkeeper.com/b/XRGF3, https://jsonkeeper.com/b/4NAKK) are hidden as base64 blobs disguised as DEV_API_KEY constants in lib/caller.js and lib/const.js. jsonkeeper.com is an anonymous public paste service — content is attacker-mutable, and the executed code runs with full require access, giving the operator arbitrary code execution on any host that loads this package's middleware. The package name evokes react/react-dom/next.js while the shipped code impersonates pino (keywords fast,logger,stream,json; files pino.js, transport, multistream, redaction; module.exports.pino = middleware), a typosquat/impersonation cover for the loader.

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

3 flagged

1.1.717.2.717.2.8

Indicators of compromise (SHA-256)

2a7b3360c09fca3400981d3d0d4c5e8a72c8193e0841c5d2eceb193a08fc440e

0972af1bf8dd73b997728e3aefd1706db878fd30639489746803b338c5b64be5

5c0e1b68083517d6b862db7f0e924e39e1b6535d50605607d4e963e8dd582b75

8e7369fd2dd1ba9002d2c693ba08c553c7c6fef54dba372146c11f20b43607aa

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for react-next-dom (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-next-dom across your stack and pipelines.
If you installed it — respond
react-next-dom is a typosquat — you almost certainly intended a legitimately-named package. Remove react-next-dom, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If react-next-dom 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.
How O3 protects you
O3 blocks react-next-dom 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. react-next-dom on npm has been identified as a malicious package (versions 1.1.7, 17.2.7, 17.2.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-99rj-fjph-w44mRLMA-2026-05258IN-MAL-2026-009250

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks react-next-dom-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database