Which versions of jwtenv are malicious?

The following npm versions of jwtenv are flagged malicious: 1.1.7. Treat any of these as compromised.

How do I remediate jwtenv if I installed it?

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

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

Yes — jwtenv is associated with the RLMA-2026-01383 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 jwtenv across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for jwtenv (version 1.1.7).

Malicious package

jwtenvnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

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

Malicious code in jwtenv (npm)

MAL-2026-1758

Immediate action

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

npm uninstall jwtenv

What this malware does

The package jwtenv was found to contain malicious code.

Malicious versions

1 flagged

1.1.7

Indicators of compromise (SHA-256)

67bf61e147e4bdd171748eee5ac722352125b555415bb65903d86313e389c14f

4ffb1c87b403f5fe445c727f61a0295c9614afddf588d99fb1fefbbe92d2abb6

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01383

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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