Critical Malicious Code Vulnerability in rush-plugins Package

rush-plugins Updated 02 Oct 2025

Summary

13/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6955: Malicious code in rush-plugins (npm). Affects rush-plugins versions >= 999.0.0. 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 rush-plugins package is a collection of plugins designed to enhance the functionality of the Rush build orchestration tool used in JavaScript projects. It allows developers to manage and streamline their build processes effectively. However, this package has been identified to communicate with a domain associated with malicious activity, posing a significant security risk to applications that utilize it.

Vulnerability Detail

The vulnerability arises from the rush-plugins package's communication with a domain linked to malicious activities. This could potentially lead to data breaches, unauthorized access, or the execution of harmful code within applications that depend on this package. The issue was introduced in version 999.0.0 and has been classified as a critical security concern due to its implications for user data and application integrity.

How To Fix

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

npm uninstall rush-plugins

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 remove the rush-plugins package from your project until a secure version is released. This can be done using the command: 'npm uninstall rush-plugins'.

Conclusion

The rush-plugins package has a critical vulnerability that allows communication with a malicious domain, posing significant risks to applications. It is crucial to update the package to a secure version or remove it until a fix is available. Utilizing tools like Vulert can help monitor your application for such vulnerabilities effectively.

See every vulnerability recorded for rush-plugins →

Share this vulnerability

FAQ

rush-plugins is a set of plugins that enhance the functionality of the Rush build orchestration tool for JavaScript projects.

The vulnerability involves the rush-plugins package communicating with a domain associated with malicious activities, posing risks to application security.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

As a workaround, consider uninstalling the rush-plugins package until a secure version is available.

The vulnerability was identified by Amazon Inspector, a security assessment service.

How To Fix

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

npm uninstall rush-plugins

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