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)
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for reactjs-risk (6 malicious versions).
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.
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
Campaign
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.