Malicious Code Vulnerability in dotenv-mono-cli Package

dotenv-mono-cli Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1712: Malicious code in dotenv-mono-cli (npm). Affects dotenv-mono-cli versions 3.3.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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

dotenv-mono-cli is a Node.js package designed to load environment variables from a .env file into process.env, facilitating configuration management for applications. It is widely used in JavaScript projects to streamline the handling of sensitive information such as API keys and database credentials. However, the package has been identified to contain malicious code that poses significant security risks to users.

Vulnerability Detail

The vulnerability in dotenv-mono-cli arises from the presence of malicious code that can execute harmful actions on the user's system. This code can potentially lead to unauthorized access to sensitive data, data corruption, or even system compromise. The malicious nature of this code was identified by security researchers from ReversingLabs, who reported the issue on March 18, 2026. The affected version is 3.3.5, and users are urged to take immediate action to mitigate the risks associated with this vulnerability.

How To Fix

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

npm uninstall dotenv-mono-cli

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

As a temporary workaround, users can remove the dotenv-mono-cli package from their project until a safe version is confirmed. This can be done using the following command:

npm uninstall dotenv-mono-cli

This will prevent any potential exploitation of the malicious code while you seek an alternative solution.

Conclusion

The dotenv-mono-cli package has been found to contain malicious code that poses significant risks to users. It is crucial to update the package to the latest version or uninstall it until a safe version is available. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for dotenv-mono-cli →

Share this vulnerability

FAQ

dotenv-mono-cli is a Node.js package that helps developers manage environment variables in their applications by loading them from a .env file.

The malicious code can execute harmful actions on the user's system, potentially leading to unauthorized access to sensitive data or system compromise.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.

If you cannot update the package right away, consider uninstalling it temporarily to mitigate the risk of exploitation.

The vulnerability was reported by security researchers from ReversingLabs, who specialize in identifying and analyzing malicious software.

How To Fix

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

npm uninstall dotenv-mono-cli

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