Malicious Code Detected in equip_components Package - Immediate Action Required

equip_components Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19754: Malicious code in equip_components (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 equip_components package is a library used in the npm ecosystem, designed to facilitate the development of web applications by providing reusable components. However, it has been identified to contain malicious code, posing a significant risk to applications that utilize it. This vulnerability can lead to unauthorized access, data breaches, and other security threats.

Vulnerability Detail

The vulnerability in the equip_components package originates from the inclusion of malicious code within its codebase. This code can execute harmful actions without the user's consent, potentially compromising the integrity and security of the applications that depend on it. The malicious nature of this vulnerability can lead to severe ramifications, including data theft, unauthorized system access, and the potential for further exploitation within the affected environment.

How To Fix

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

npm uninstall equip_components

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 workaround, you can remove the equip_components package from your project and replace it with an alternative library that offers similar functionality without the associated risks. You can do this by executing the following command: npm uninstall equip_components.

Conclusion

The equip_components package has been found to contain malicious code, posing a significant threat to applications that utilize it. Immediate action is required to remove the package and replace it with a secure alternative. Regular monitoring for vulnerabilities is crucial to maintaining application security.

See every vulnerability recorded for equip_components →

Share this vulnerability

FAQ

equip_components is an npm package designed to provide reusable components for web application development.

The malicious code was identified through security audits and reports from security tools like Amazon Inspector.

Using the equip_components package can lead to unauthorized access, data breaches, and other security vulnerabilities in your application.

Yes, you can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

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

How To Fix

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

npm uninstall equip_components

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