Which versions of react-jsonwebtoken are malicious?

The following npm versions of react-jsonwebtoken are flagged malicious: 9.0.3, 9.0.4, 9.0.5. Treat any of these as compromised.

How do I remediate react-jsonwebtoken if I installed it?

react-jsonwebtoken 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-jsonwebtoken — how do I know if it already compromised me?

If react-jsonwebtoken was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is react-jsonwebtoken part of a known attack campaign?

Yes — react-jsonwebtoken is associated with the IN-MAL-2026-009640, IN-MAL-2026-009639, IN-MAL-2026-009641 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-jsonwebtoken across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for react-jsonwebtoken (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-jsonwebtoken across your stack and pipelines.

Malicious package

react-jsonwebtokennpm

Malicious code in react-jsonwebtoken (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10132

Immediate action

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

npm uninstall react-jsonwebtoken

What this malware does

Package name mimics the widely-used 'jsonwebtoken' library and falsely declares 'auth0' as author, while the repository URL points to the unrelated 'github.com/radix-ui/primitives'. On require(), decode.js unconditionally invokes a helper (getThirdCookie) that performs an HTTPS GET to https://jsonkeeper.com/b/E69V3 — an anonymous, mutable paste endpoint — and passes the response body into new Function.constructor("require", errCode), then executes the resulting function with the host's require. This grants the remote content full Node.js capabilities on the consumer's machine as soon as any code loads the module. The code path is hidden behind a benign-sounding helper name and uses indirect Function construction to evade simple pattern matching. The combination of impersonated author metadata, name confusion with a top-100 auth library, and an obfuscated require-time remote-code loader is an unambiguous supply-chain attack.

Malicious versions

3 flagged

9.0.39.0.49.0.5

Indicators of compromise (SHA-256)

2b46ca6ae72ce6f079c34ec6d1d1d2be46b36fe429374393f0fe57539fe56ee3

3792a6c469fb9e9266f414755e5e9ab46857e9f95a9852ea66261bcdbc80a4eb

4640784a797c88ab6742f7da14e8e13e7e33bf16a9a93c31104ffb130e051dbc

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for react-jsonwebtoken (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-jsonwebtoken across your stack and pipelines.
If you installed it — respond
react-jsonwebtoken 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-jsonwebtoken was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks react-jsonwebtoken before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. react-jsonwebtoken on npm has been identified as a malicious package (versions 9.0.3, 9.0.4, 9.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009640IN-MAL-2026-009639IN-MAL-2026-009641

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks react-jsonwebtoken-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