Critical Malicious Code Vulnerability in gulp-inject-envs Package

gulp-inject-envs Updated 25 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191105: Malicious code in gulp-inject-envs (npm). Affects gulp-inject-envs versions 1.2.1 – 1.2.2. 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

gulp-inject-envs is an npm package designed to facilitate the injection of environment variables into applications. It is commonly used in Node.js projects to manage configuration settings dynamically. However, this package has been compromised, leading to severe security risks for any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the gulp-inject-envs 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 origin of this malicious code has been traced back to a specific commit in the package's repository, and it poses a significant threat to the integrity and confidentiality of affected systems.

How To Fix

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

npm uninstall gulp-inject-envs

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, you can avoid using the gulp-inject-envs package and replace its functionality with alternative methods for managing environment variables. For example, consider using dotenv or similar packages that do not have known vulnerabilities.

Conclusion

The gulp-inject-envs package has been compromised with malicious code, posing a significant risk to any systems using it. Immediate action is required to remove the package and secure any exposed secrets. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities in your software dependencies.

See every vulnerability recorded for gulp-inject-envs →

Share this vulnerability

FAQ

Immediately remove the package and rotate any sensitive information that may have been exposed.

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

Failure to address this vulnerability can lead to unauthorized access to sensitive data, potential data breaches, and complete system compromise.

Yes, tools like Vulert can monitor your package-lock.json file to alert you in real-time for any open-source vulnerabilities.

While many npm packages are safe, it's essential to regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities.

How To Fix

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

npm uninstall gulp-inject-envs

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