Malicious code in react-paginate-v5 (npm)
Description
The npm package [email protected] is a malicious package designed as a dependency confusion probe. It masquerades under a name similar to the legitimate react-paginate package but uses an implausibly high version number to override internal packages. Upon installation, it executes a preinstall script that performs a DNS lookup to an attacker-controlled domain, confirming the package's installation and revealing resolver metadata. The package has no legitimate functionality and can potentially execute arbitrary shell commands during installation.
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
[email protected] is a malicious npm package published as a dependency confusion probe. It exploits the npm install lifecycle by declaring a preinstall script that runs a DNS query to a canary token domain controlled by an attacker or researcher. This DNS query acts as a beacon, confirming installation and leaking resolver metadata to the operator. The package name closely resembles a popular legitimate package (react-paginate) and uses a high version number (99.0.0) to win resolution precedence over internal packages with the same name. Although the current payload only performs a DNS lookup, the install-time execution capability could be used to run arbitrary shell commands. The package itself provides no legitimate functionality.
Potential Impact
The primary impact is the exfiltration of installation occurrence and DNS resolver metadata to an attacker-controlled domain, which can reveal internal network information and hosts where the package was installed. While the current payload is limited to a DNS beacon, the underlying mechanism allows execution of arbitrary commands during installation, posing a risk of more severe compromise if exploited with malicious payloads.
Mitigation Recommendations
No official patch or fix is available as this is a malicious package published to the public npm registry. The best mitigation is to avoid installing packages with suspicious names and implausible version numbers, especially those that resemble internal or popular packages. Implement strict package name allowlisting and verify package provenance before installation. Monitor for unexpected preinstall scripts in dependencies. Since this is not a cloud service, remediation depends on user and organizational controls.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-17777
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6acc00a32cdf04f656fecb2d
Added to database: 10/11/2026, 21:33:23 UTC
Last enriched: 10/11/2026, 21:43:56 UTC
Last updated: 10/11/2026, 21:43:56 UTC
Views: 3
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.