Which versions of jsonwebjstoken are malicious?

The following npm versions of jsonwebjstoken are flagged malicious: 9.0.2, 9.0.3, 9.0.4, 9.0.5, 9.0.6. Treat any of these as compromised.

How do I remediate jsonwebjstoken if I installed it?

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

If jsonwebjstoken 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 jsonwebjstoken part of a known attack campaign?

Yes — jsonwebjstoken is associated with the GHSA-wxc7-cg7f-7f7h, RLMA-2025-05050, RLUA-2026-01380 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 jsonwebjstoken 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 jsonwebjstoken (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jsonwebjstoken across your stack and pipelines.

Malicious package

jsonwebjstokennpm

jsonwebjstoken is a confirmed malicious npm package (MAL-2025-47319) that steals credentials and exfiltrates sensitive data (malicious versions 9.0.2, 9.0.3, 9.0.4…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in jsonwebjstoken (npm)

MAL-2025-47319

Immediate action

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

npm uninstall jsonwebjstoken

What this malware does

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.

Malicious versions

5 flagged

9.0.29.0.39.0.49.0.59.0.6

Indicators of compromise (SHA-256)

d5866f0ff5443038e8141f9674f6d4d83ef512aba824b8a430cbd459f9dfba71

9234641f4ccd9f2e771be253c42cc5b6de5239078c6d69f67c69acdf54043e85

d0c8e9be52661c4f3d567a1543cf0f75337c53c10fe8fd085be7cc5315804d35

2aea1b642150e0beacafc3bbb675e8857e403dae184dd5a5d1afd3cea5637024

0f91426ea03071f89c60e3f121267b8a189dca4e76492af9e1e8b1bfa1f5cce8

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 jsonwebjstoken (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jsonwebjstoken across your stack and pipelines.
If you installed it — respond
jsonwebjstoken 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 jsonwebjstoken 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 jsonwebjstoken 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. jsonwebjstoken on npm has been identified as a malicious package (versions 9.0.2, 9.0.3, 9.0.4, 9.0.5, 9.0.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-wxc7-cg7f-7f7hRLMA-2025-05050RLUA-2026-01380

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks jsonwebjstoken-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