Malicious code in reactjs-risk (npm)
The npm package 'reactjs-risk' versions 99.17.1 and 99.17.2 contains malicious code that executes during installation. Its preinstall script collects host identity metadata including hostname, username, and platform, encodes this data, and sends it via DNS lookup to a third-party domain without user consent. The package's main entry point is a non-functional stub, indicating the sole purpose is to exfiltrate installer information. This behavior is deliberately obfuscated to evade detection.
AI Analysis
Technical Summary
The 'reactjs-risk' npm package (versions 99.17.1 and 99.17.2) includes a preinstall lifecycle script that collects sensitive host metadata such as os.hostname(), the output of the 'whoami' command, and os.platform(). This data is hex-encoded and sent via a DNS A-record lookup to a canarytokens.com subdomain controlled by a third party. The package uses string concatenation to obfuscate the loading of the 'dns' module and the execution of the 'whoami' command. The main entry point of the package is an empty stub, confirming that the package's only functionality is the unauthorized exfiltration of installer identity data during installation.
Potential Impact
Installing this package results in the unauthorized transmission of the installer's hostname, username, and platform information to a third-party DNS endpoint without user consent. This can lead to privacy violations and potential reconnaissance by malicious actors. There is no indication of further malicious payloads or code execution beyond this data exfiltration.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid installing the 'reactjs-risk' package versions 99.17.1 and 99.17.2. Verify package authenticity before installation and consider using trusted package registries and tools that detect malicious packages. Monitor for updates from the package maintainer or npm regarding remediation.
Malicious code in reactjs-risk (npm)
Description
The npm package 'reactjs-risk' versions 99.17.1 and 99.17.2 contains malicious code that executes during installation. Its preinstall script collects host identity metadata including hostname, username, and platform, encodes this data, and sends it via DNS lookup to a third-party domain without user consent. The package's main entry point is a non-functional stub, indicating the sole purpose is to exfiltrate installer information. This behavior is deliberately obfuscated to evade detection.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The 'reactjs-risk' npm package (versions 99.17.1 and 99.17.2) includes a preinstall lifecycle script that collects sensitive host metadata such as os.hostname(), the output of the 'whoami' command, and os.platform(). This data is hex-encoded and sent via a DNS A-record lookup to a canarytokens.com subdomain controlled by a third party. The package uses string concatenation to obfuscate the loading of the 'dns' module and the execution of the 'whoami' command. The main entry point of the package is an empty stub, confirming that the package's only functionality is the unauthorized exfiltration of installer identity data during installation.
Potential Impact
Installing this package results in the unauthorized transmission of the installer's hostname, username, and platform information to a third-party DNS endpoint without user consent. This can lead to privacy violations and potential reconnaissance by malicious actors. There is no indication of further malicious payloads or code execution beyond this data exfiltration.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid installing the 'reactjs-risk' package versions 99.17.1 and 99.17.2. Verify package authenticity before installation and consider using trusted package registries and tools that detect malicious packages. Monitor for updates from the package maintainer or npm regarding remediation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-17339
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6abd306a2a4e24523d3384d7
Added to database: 09/30/2026, 15:53:14 UTC
Last enriched: 09/30/2026, 15:54:38 UTC
Last updated: 09/30/2026, 22:34:24 UTC
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.