Which versions of react-paginate-v5 are malicious?

The following npm versions of react-paginate-v5 are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate react-paginate-v5 if I installed it?

react-paginate-v5 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.

I already installed react-paginate-v5 — how do I know if it already compromised me?

If react-paginate-v5 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.

Is react-paginate-v5 part of a known attack campaign?

Yes — react-paginate-v5 is associated with the IN-MAL-2026-021429 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find react-paginate-v5 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for react-paginate-v5 (version 99.0.0).

Malicious package

react-paginate-v5npm

Advisory published Oct 11, 2026Updated Oct 11, 2026

react-paginate-v5 is a confirmed malicious npm package (MAL-2026-17777) that steals credentials and exfiltrates sensitive data (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in react-paginate-v5 (npm)

MAL-2026-17777

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall react-paginate-v5

What this malware does

[email protected] is a dependency-confusion probe published under a name resembling the popular react-paginate package and pinned to an implausibly high version (99.0.0) to win resolution against an internal package. Its package.json declares a preinstall lifecycle script that runs nslookup dep-confusion-poc.2chsn9exkdupkr3cxed7vp7sk.canarytokens.com, which fires automatically on npm install and emits a DNS query from the installer's resolver to an attacker/researcher-controlled canary subdomain. The subdomain label (dep-confusion-poc) self-identifies the operation as a dependency-confusion test. The DNS lookup confirms successful installation to the operator of the canary token, identifying hosts and networks where an internal package name was shadowed by this public squat. While the beacon itself only exfiltrates the fact of installation plus resolver metadata, the same install-time execution primitive can carry any shell command, and the package has no legitimate functionality.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

2c0f91fe35323a6f47033b90ebaf88498a36fd7e8e933711b2cf301dba2e4759

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for react-paginate-v5 (version 99.0.0).
If you installed it — respond
react-paginate-v5 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 react-paginate-v5 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. react-paginate-v5 on npm has been identified as a malicious package (version 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021429

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks react-paginate-v5-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database