Malicious Code Vulnerability in jwtenv Package

jwtenv Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1758: Malicious code in jwtenv (npm). Affects jwtenv versions 1.1.7. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

jwtenv is an npm package designed for managing JSON Web Tokens (JWTs) in JavaScript applications. It provides developers with tools to create, sign, and verify JWTs easily. However, the package has been found to contain malicious code that can compromise the security of applications using it, making it critical for developers to be aware of this issue.

Vulnerability Detail

The vulnerability in jwtenv stems from the inclusion of malicious code that can execute unauthorized actions within an application. This code can potentially lead to data breaches, unauthorized access, and other security risks. The malicious version of the package was identified in version 1.1.7, and it is crucial for developers to understand the implications of using this compromised package.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall jwtenv

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

If you cannot update the package immediately, consider removing jwtenv from your project and replacing it with an alternative library that provides similar functionality without the associated risks.

Conclusion

The jwtenv package has been identified as containing malicious code that poses significant security risks to applications. It is essential for developers to update to a secure version or find alternatives to mitigate these risks. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for jwtenv →

Share this vulnerability

FAQ

jwtenv is used for managing JSON Web Tokens (JWTs) in JavaScript applications, providing tools for creating, signing, and verifying tokens.

You can check if your application is affected by using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to use the Vulert playground without signup.

The malicious code can lead to unauthorized access, data breaches, and other security vulnerabilities within applications that utilize the compromised package.

Yes, you can remove jwtenv from your project and look for alternative libraries that provide similar functionality without the security risks.

The vulnerability was reported by ReversingLabs, a security research organization specializing in identifying malicious packages.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall jwtenv

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback