Critical Malicious Code Vulnerability in @uniconvex/dotenv Package

@uniconvex/dotenv Updated 10 Feb 2026

Summary

10/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-829: Malicious code in @uniconvex/dotenv (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 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

The @uniconvex/dotenv package is a Node.js library used for loading environment variables from a .env file into process.env. It is commonly utilized in various applications to manage configuration settings securely. However, this package has been identified to contain malicious code, posing significant security risks to systems utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the @uniconvex/dotenv package. This code can compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code means that simply removing the package may not eliminate all traces of the compromise, as full control of the affected system may have been granted to an external entity.

How To Fix

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

npm uninstall @uniconvex/dotenv

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, the best workaround is to uninstall the @uniconvex/dotenv package and avoid using it until a secure alternative is identified. You can uninstall the package using the following command: npm uninstall @uniconvex/dotenv.

Conclusion

The @uniconvex/dotenv package contains malicious code that poses significant security risks. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to monitor their applications for vulnerabilities using tools like Vulert.

See every vulnerability recorded for @uniconvex/dotenv →

Share this vulnerability

FAQ

The malicious code can lead to unauthorized access to sensitive information and full compromise of the affected system.

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

Immediately uninstall the package and rotate any secrets or keys stored on the affected system.

While removing the package is essential, there is no guarantee that all malicious software will be eliminated. It is advisable to perform a thorough security audit of the system.

Yes, consider using other well-known and trusted dotenv packages such as dotenv or dotenv-safe, which do not have known vulnerabilities.

How To Fix

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

npm uninstall @uniconvex/dotenv

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