Which versions of jwt-path are malicious?

The following npm versions of jwt-path are flagged malicious: 3.1.3. Treat any of these as compromised.

How do I remediate jwt-path if I installed it?

Remove jwt-path from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed jwt-path — how do I know if it already compromised me?

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

Yes — jwt-path is associated with the RLMA-2026-05134, RLUA-2026-06294 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 jwt-path across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for jwt-path (version 3.1.3).

Malicious package

jwt-pathnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

jwt-path is a confirmed malicious npm package (MAL-2026-7306) that executes malicious code on install (malicious version 3.1.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in jwt-path (npm)

MAL-2026-7306

Immediate action

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

npm uninstall jwt-path

Malicious versions

1 flagged

3.1.3

Indicators of compromise (SHA-256)

fe51bc4a020ba5cafe984ccb5c8bbafb6330397c8bb88bdb3b565ce50eb6ab22

7dae6e7a2bb7e7073be964233d9e036ae94d602ef831d3e375c19f554bc88337

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for jwt-path (version 3.1.3).
If you installed it — respond
Remove jwt-path from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If jwt-path 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. jwt-path on npm has been identified as a malicious package (version 3.1.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-05134RLUA-2026-06294

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks jwt-path-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database