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

reactjs-risknpm

Advisory published Updated

reactjs-risk is a confirmed malicious npm package (MAL-2026-17339) that steals credentials and exfiltrates sensitive data (malicious versions 99.9.9, 99.12.0, 99.17.0…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in reactjs-risk (npm)

MAL-2026-17339
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall reactjs-risk

What this malware does

The package's preinstall lifecycle script collects host identity metadata from the installer machine — os.hostname(), the output of whoami/os.userInfo().username, and os.platform() — hex-encodes the values, and issues a DNS A-record lookup for <hex>.768hgkqn53abdemu8ikzkel4g.canarytokens.com, causing the installer's hostname, username, and platform to be transmitted to the canarytoken operator on every npm install. The dns module is loaded via string concatenation ('d'+'n'+'s') and the whoami command is similarly split, indicating deliberate obfuscation of the module and command names. The package's declared main entry is an empty stub with no library functionality, so the preinstall beacon is the package's only behavior. Installing this package auto-executes an unauthenticated exfiltration of installer identity metadata to a third-party DNS endpoint the installer did not opt into.

The OpenSSF Package Analysis project identified 'reactjs-risk' @ 99.17.1 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

6 flagged
99.9.999.12.099.17.099.17.199.17.299.17.4

Indicators of compromise (SHA-256)

a32a318956967c92b753750e0b607e48db7eef07d05f25c2b687f3b9612f806e
7bb6a3319bd95ae759acafaee820c331f78291170c6895d06f5c0e78c761afd2
0e58c82916c5199ef9e73a5d70f91d120312151eb5c28090d8bbf6dbf4117543
3a5dc3ce9adff40ece4797ddd3349d25cc9e587737bde995ce0038740f72c56b
54ea883450b7f65285f08f4610b55333d89153938d2618de98f2857b3b9053ca
834b02617e1065531a64b675b64d6d003f8c79f6c2fc9fd9779f259c5bf05ef4
a808d3c4997253da115154c5466b69ef5f4138bdb07398a475a20d54bfcba303
cf0f2c8b571beb70f6c3a64b36b88bad2c3566e4889e7545eb781589921761a7

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for reactjs-risk (6 malicious versions).

  2. If you installed it — respond

    reactjs-risk 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 reactjs-risk 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. reactjs-risk on npm has been identified as a malicious package (versions 99.9.9, 99.12.0, 99.17.0, 99.17.1, 99.17.2, 99.17.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020824IN-MAL-2026-020823IN-MAL-2026-020828IN-MAL-2026-020827IN-MAL-2026-020825IN-MAL-2026-020826

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks reactjs-risk-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

reactjs-risk (npm) malicious package — MAL-2026-17339 | O3 Security