Critical Malicious Code Vulnerability in dotnetenv Package

dotnetenv Updated 05 Dec 2025

Summary

05/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192320: Malicious code in dotnetenv (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 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

dotnetenv is an npm package designed to facilitate the management of environment variables in .NET applications. It allows developers to easily load environment variables from a .env file into their application, enhancing configuration management. However, this package has been compromised, leading to severe security risks for any system utilizing it.

Vulnerability Detail

The vulnerability originates from the presence of malicious code embedded within the dotnetenv package. This code can fully compromise any computer that has the package installed or running, allowing unauthorized access to sensitive information such as secrets and keys. The implications of this vulnerability are significant, as it can lead to data breaches and loss of control over the affected systems.

How To Fix

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

npm uninstall dotnetenv

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 workaround, it is advisable to avoid using the dotnetenv package until the issue is resolved. Consider using alternative packages for managing environment variables that have not been compromised.

Conclusion

The dotnetenv package has been compromised by malicious code, posing a serious threat to any systems using it. Immediate action is required to remove the package and secure sensitive information. Stay vigilant for updates and consider using alternative solutions for managing environment variables.

See every vulnerability recorded for dotnetenv →

Share this vulnerability

FAQ

dotnetenv is an npm package that helps developers manage environment variables in .NET applications by loading them from a .env file.

The malicious code can fully compromise your system, allowing unauthorized access to sensitive information and potentially leading to data breaches.

You should immediately remove the dotnetenv package and rotate any secrets or keys stored on your system from a secure machine.

Currently, there is no patched version available. It is essential to remove the package and monitor for updates.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall dotnetenv

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