Malicious Code Vulnerability in dotenv-nodejs Package

dotenv-nodejs Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1715: Malicious code in dotenv-nodejs (npm). Affects dotenv-nodejs 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 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

dotenv-nodejs is an npm package designed to load environment variables from a .env file into process.env, facilitating configuration management in Node.js applications. It is widely used for managing sensitive information such as API keys and database credentials. However, the package has been compromised, introducing malicious code that could potentially harm applications relying on it.

Vulnerability Detail

The vulnerability in dotenv-nodejs stems from the introduction of malicious code in version 3.3.5. This code can lead to unauthorized access to sensitive information and may allow attackers to execute arbitrary commands within the context of the application. The malicious package was identified by ReversingLabs, highlighting the risks associated with using compromised open-source libraries.

How To Fix

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

npm uninstall dotenv-nodejs

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, you can remove the dotenv-nodejs package from your project and manually manage environment variables without using this package. This can be done by setting environment variables directly in your operating system or using alternative libraries that are not compromised.

Conclusion

The dotenv-nodejs package has been compromised, introducing a vulnerability that can lead to serious security risks. It is crucial to update to a secure version or implement workarounds to protect your application. Regular monitoring for vulnerabilities using tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for dotenv-nodejs →

Share this vulnerability

FAQ

dotenv-nodejs is an npm package that loads environment variables from a .env file into process.env, simplifying configuration management in Node.js applications.

The malicious code was introduced in version 3.3.5 of dotenv-nodejs, as identified by security researchers at ReversingLabs.

Using the compromised version can lead to unauthorized access to sensitive information and potential execution of arbitrary commands by attackers.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.

If immediate updates are not possible, consider removing the dotenv-nodejs package and managing environment variables manually or using alternative libraries.

How To Fix

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

npm uninstall dotenv-nodejs

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