Malicious code in react-next-dom (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (8e7369fd2dd1ba9002d2c693ba08c553c7c6fef54dba372146c11f20b43607aa) react-next-dom masquerades as a React/Next.js ecosystem package but ships a pino-like surface concealing a remote code loader. The main export is a middleware factory that, when invoked, spawns `node./lib/caller.js` as a detached, stdio-ignored child process (`spawn("node", [script,...], { detached: true, stdio: "ignore" }); child.unref()`). lib/caller.js then fetches a JavaScript payload from https://jsonkeeper.com/b/D3GLF (using an `x-secret-key` header), and evaluates the response body in the host Node.js process via `new Function.constructor("require", s)(require)`, retrying up to 5 times. Additional payload URLs (https://jsonkeeper.com/b/XRGF3, https://jsonkeeper.com/b/4NAKK) are hidden as base64 blobs disguised as `DEV_API_KEY` constants in lib/caller.js and lib/const.js. jsonkeeper.com is an anonymous public paste service — content is attacker-mutable, and the executed code runs with full `require` access, giving the operator arbitrary code execution on any host that loads this package's middleware. The package name evokes react/react-dom/next.js while the shipped code impersonates pino (keywords `fast`,`logger`,`stream`,`json`; files `pino.js`, transport, multistream, redaction; `module.exports.pino = middleware`), a typosquat/impersonation cover for the loader. ## Source: ghsa-malware (2a7b3360c09fca3400981d3d0d4c5e8a72c8193e0841c5d2eceb193a08fc440e) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
AI Analysis
Technical Summary
The react-next-dom package in specific npm versions (17.2.7, 1.1.7, and 17.2.8) has been identified as containing malicious code. Any system with these versions installed or running is considered fully compromised, implying that attackers may have gained complete control over the system. The advisory recommends immediate rotation of all secrets and keys from a different, secure machine. Due to the nature of the compromise, simply uninstalling the package does not guarantee removal of all malicious artifacts or backdoors introduced by the package.
Potential Impact
Full system compromise on any computer with the affected react-next-dom package versions installed or running. Attackers may have access to all secrets and keys stored on the system. The integrity and confidentiality of the affected system are severely impacted.
Mitigation Recommendations
Remove the malicious react-next-dom package versions from the system. Immediately rotate all secrets and keys from a secure, uncompromised device. Because the system may be fully compromised, consider rebuilding or thoroughly cleaning the affected machine to ensure removal of all malicious components. No official patch or fix is available; remediation relies on removal and secret rotation.
Malicious code in react-next-dom (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (8e7369fd2dd1ba9002d2c693ba08c553c7c6fef54dba372146c11f20b43607aa) react-next-dom masquerades as a React/Next.js ecosystem package but ships a pino-like surface concealing a remote code loader. The main export is a middleware factory that, when invoked, spawns `node./lib/caller.js` as a detached, stdio-ignored child process (`spawn("node", [script,...], { detached: true, stdio: "ignore" }); child.unref()`). lib/caller.js then fetches a JavaScript payload from https://jsonkeeper.com/b/D3GLF (using an `x-secret-key` header), and evaluates the response body in the host Node.js process via `new Function.constructor("require", s)(require)`, retrying up to 5 times. Additional payload URLs (https://jsonkeeper.com/b/XRGF3, https://jsonkeeper.com/b/4NAKK) are hidden as base64 blobs disguised as `DEV_API_KEY` constants in lib/caller.js and lib/const.js. jsonkeeper.com is an anonymous public paste service — content is attacker-mutable, and the executed code runs with full `require` access, giving the operator arbitrary code execution on any host that loads this package's middleware. The package name evokes react/react-dom/next.js while the shipped code impersonates pino (keywords `fast`,`logger`,`stream`,`json`; files `pino.js`, transport, multistream, redaction; `module.exports.pino = middleware`), a typosquat/impersonation cover for the loader. ## Source: ghsa-malware (2a7b3360c09fca3400981d3d0d4c5e8a72c8193e0841c5d2eceb193a08fc440e) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
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 react-next-dom package in specific npm versions (17.2.7, 1.1.7, and 17.2.8) has been identified as containing malicious code. Any system with these versions installed or running is considered fully compromised, implying that attackers may have gained complete control over the system. The advisory recommends immediate rotation of all secrets and keys from a different, secure machine. Due to the nature of the compromise, simply uninstalling the package does not guarantee removal of all malicious artifacts or backdoors introduced by the package.
Potential Impact
Full system compromise on any computer with the affected react-next-dom package versions installed or running. Attackers may have access to all secrets and keys stored on the system. The integrity and confidentiality of the affected system are severely impacted.
Mitigation Recommendations
Remove the malicious react-next-dom package versions from the system. Immediately rotate all secrets and keys from a secure, uncompromised device. Because the system may be fully compromised, consider rebuilding or thoroughly cleaning the affected machine to ensure removal of all malicious components. No official patch or fix is available; remediation relies on removal and secret rotation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-6825
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-99rj-fjph-w44m"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a4c341527e9c797195f7ed9
Added to database: 07/06/2026, 23:02:45 UTC
Last enriched: 07/06/2026, 23:17:59 UTC
Last updated: 07/30/2026, 22:20:21 UTC
Views: 44
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.