Critical Malicious Code Vulnerability in minify-replace Package

minify-replace Updated 18 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1503: Malicious code in minify-replace (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The minify-replace package is a tool used in the npm ecosystem for replacing strings in minified files, often utilized in web development to optimize code. However, this package has been compromised, leading to severe security risks for any system that has it installed. The malicious code embedded in this package can grant unauthorized access to attackers, putting sensitive data at risk.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code in the minify-replace package, identified as GHSA-c4qg-vqr5-vwq8. This code can fully compromise any computer running the package, allowing attackers to access secrets and keys stored on the system. The implications are severe, as the malicious code may persist even after the package is removed, indicating a potential backdoor for continued access.

How To Fix

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

npm uninstall minify-replace

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 minify-replace package entirely. Use the following command in your terminal: npm uninstall minify-replace. Additionally, consider using alternative packages that do not have known vulnerabilities.

Conclusion

The minify-replace package has been compromised with malicious code, posing a significant threat to systems that have it installed. Immediate action is required to remove the package and secure sensitive information. Regular monitoring for vulnerabilities, such as through Vulert, can help maintain the security of your applications.

See every vulnerability recorded for minify-replace →

Share this vulnerability

FAQ

Immediately uninstall the package and rotate any sensitive information stored on the affected system.

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

As of now, there is no patched version available. The recommended action is to uninstall the package.

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

While removing the package is essential, there is no guarantee that all malicious software has been eliminated. A thorough security audit is recommended.

How To Fix

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

npm uninstall minify-replace

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