Malicious Code Detected in environment-inc Package - Security Alert

environment-inc Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19686: Malicious code in environment-inc (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The environment-inc package is an npm library designed to facilitate environment variable management in Node.js applications. It allows developers to easily access and manipulate environment variables, which are crucial for configuring applications in different environments. However, the package has been identified to contain malicious code, posing significant security risks to users.

Vulnerability Detail

The vulnerability in the environment-inc package stems from the inclusion of malicious code that can compromise the security of applications utilizing this package. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious code was introduced in version 0 and has been flagged as a critical security issue that requires immediate attention.

How To Fix

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

npm uninstall environment-inc

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 temporary measure, consider removing the environment-inc package from your project until a secure version is released. You can do this by executing the command: npm uninstall environment-inc. This will help mitigate the risk of exposure to the malicious code.

Conclusion

The discovery of malicious code in the environment-inc package poses a significant threat to users. It is crucial to take immediate action by updating or removing the package to safeguard your applications. Stay informed about updates and utilize tools like Vulert for ongoing monitoring of vulnerabilities.

See every vulnerability recorded for environment-inc →

Share this vulnerability

FAQ

The environment-inc package is an npm library used for managing environment variables in Node.js applications.

The malicious code can potentially lead to unauthorized access and data breaches within applications that utilize the environment-inc package.

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

If an immediate update is not possible, consider removing the environment-inc package from your project as a temporary workaround.

Detailed information about the vulnerability can be found on the GitHub repository of the malicious packages project.

How To Fix

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

npm uninstall environment-inc

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