Malicious Code Vulnerability in dotenv-cli-node Package

dotenv-cli-node Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1710: Malicious code in dotenv-cli-node (npm). Affects dotenv-cli-node versions 2.4.5. 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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

dotenv-cli-node is an npm package that allows users to load environment variables from a .env file into the process environment. This package is commonly used in Node.js applications to manage configuration settings securely. However, it has been identified to contain malicious code, which poses a significant security risk to users relying on it for environment variable management.

Vulnerability Detail

The vulnerability in dotenv-cli-node stems from the presence of malicious code that can compromise the security of applications using this package. This code may lead to unauthorized access to sensitive information or allow attackers to execute arbitrary commands within the application. The malicious code was introduced in version 2.4.5, and users of this version are particularly at risk. The origin of this vulnerability is linked to the package being compromised, which highlights the importance of monitoring dependencies for security threats.

How To Fix

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

npm uninstall dotenv-cli-node

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 immediate updating is not possible, consider temporarily removing the dotenv-cli-node package from your project until a secure version is available. This can be done by running: npm uninstall dotenv-cli-node. Additionally, you can manually manage environment variables without this package as a temporary measure.

Conclusion

The dotenv-cli-node package has been identified to contain malicious code, posing a significant risk to applications that utilize it. Users are advised to update to the latest version to mitigate this vulnerability. Monitoring tools like Vulert can assist in identifying such vulnerabilities in real-time.

See every vulnerability recorded for dotenv-cli-node →

Share this vulnerability

FAQ

dotenv-cli-node is an npm package used to load environment variables from a .env file into the process environment for Node.js applications.

You can check if your application is affected by using Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to analyze your package-lock.json without needing to sign up.

If you cannot update the package right away, consider uninstalling dotenv-cli-node temporarily and managing your environment variables manually.

The risks include unauthorized access to sensitive information and the potential for attackers to execute arbitrary commands within your application.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert and keep your packages updated to the latest secure versions.

How To Fix

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

npm uninstall dotenv-cli-node

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