Critical Malicious Code Vulnerability in dot-env-buffer Package

dot-env-buffer Updated 20 Jan 2026

Summary

20/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-358: Malicious code in dot-env-buffer (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

The dot-env-buffer package is a Node.js library used for managing environment variables in applications. It allows developers to load environment variables from a .env file into process.env, making it easier to configure applications. 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 dot-env-buffer package. This code can fully compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The ramifications include complete control of the affected system by an external entity, making it imperative for users to act swiftly 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 dot-env-buffer

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 recommended to rotate all secrets and keys stored on the affected computer from a different, secure machine. This ensures that any compromised credentials are no longer valid.

Conclusion

The dot-env-buffer package has been compromised, posing a significant security risk to any system using it. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for dot-env-buffer →

Share this vulnerability

FAQ

dot-env-buffer is a Node.js library that helps manage environment variables by loading them from a .env file into the application's process environment.

The malicious code can give an external entity full control over your system, allowing them to access sensitive information and potentially install further malicious software.

Immediately remove the dot-env-buffer package and rotate any secrets or keys stored on the affected system. Consider using a secure machine for this process.

Yes, you can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software. You can check your application for vulnerabilities using the Vulert playground without any signup.

Not necessarily. While removing the package is crucial, there is no guarantee that all malicious software resulting from its installation will be removed.

How To Fix

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

npm uninstall dot-env-buffer

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