Critical Malicious Code Vulnerability in dotenv-intended Package

dotenv-intended Updated 09 Jan 2026

Summary

09/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-174: Malicious code in dotenv-intended (npm). Affected versions are not published. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The dotenv-intended package is an npm library designed to manage environment variables in Node.js applications. It allows developers to load environment variables from a .env file into process.env, facilitating the management of configuration settings. However, this package has been compromised, leading to severe security risks for any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the dotenv-intended package. This code can fully compromise any computer that has the package installed or running, potentially allowing unauthorized access to sensitive information such as secrets and keys. The origin of this issue is linked to a malicious actor who has manipulated the package, making it imperative for users to take immediate action to secure their systems.

How To Fix

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

npm uninstall dotenv-intended

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

Currently, there are no effective workarounds to mitigate the risks posed by the malicious code in the dotenv-intended package. The only recommended action is to uninstall the package as described above.

Conclusion

The dotenv-intended package has been compromised with malicious code, posing significant security risks to any system using it. Immediate uninstallation of the package and rotation of sensitive information is essential to mitigate these risks. Users are encouraged to utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for dotenv-intended →

Share this vulnerability

FAQ

You should immediately uninstall the package and rotate any secrets or keys stored on the affected machine.

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

No, there is currently no patched version available for the dotenv-intended package. The only solution is to remove it.

Failing to address this vulnerability could lead to unauthorized access to sensitive information, potentially compromising your entire system.

It is highly discouraged to use dotenv-intended due to the severe security risks associated with the malicious code embedded in the package.

How To Fix

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

npm uninstall dotenv-intended

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