Critical Malicious Code Vulnerability in dotenv-intend Package

dotenv-intend Updated 04 Dec 2025

Summary

03/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192290: Malicious code in dotenv-intend (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

dotenv-intend is an npm package designed to facilitate the loading of environment variables from .env files into Node.js applications. It is widely used in various projects to manage configuration settings securely. However, this package has been compromised, leading to significant security risks for any application that utilizes it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the dotenv-intend 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 malicious code can persist even after the package is removed, as it may have granted full control of the system to an external entity.

How To Fix

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

npm uninstall dotenv-intend

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

There are no effective workarounds for this vulnerability other than removing the package entirely and ensuring that the system is secure.

Conclusion

The dotenv-intend package has been found to contain malicious code that poses a severe security risk. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities in your software.

See every vulnerability recorded for dotenv-intend →

Share this vulnerability

FAQ

You should remove the dotenv-intend package immediately and rotate any secrets or keys stored on the affected system.

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

Failing to address this vulnerability can lead to unauthorized access to sensitive information, potential data breaches, and full system compromise.

If your system has been compromised, it is recommended to perform a thorough security audit, remove all malicious software, and restore from a secure backup.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, and ensure to keep your packages updated to their latest versions.

How To Fix

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

npm uninstall dotenv-intend

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