Critical Malicious Code Vulnerability in react-component-taggers Package

react-component-taggers Updated 25 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190989: Malicious code in react-component-taggers (npm). Affects react-component-taggers versions 0.1.9. 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 react-component-taggers package is an npm library designed for tagging React components, enabling developers to manage and organize their components efficiently. However, it has been found to contain malicious code that poses significant security risks to any system utilizing this package.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the react-component-taggers package. This code can compromise the entire system where the package is installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code means that any computer running this package should be considered fully compromised, leading to potential data breaches and loss of control over the system.

How To Fix

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

npm uninstall react-component-taggers

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 workaround, ensure that the package is uninstalled using the command: npm uninstall react-component-taggers. Additionally, monitor your system for any unusual activity and consider using security tools to scan for any remaining malicious software.

Conclusion

The discovery of malicious code within the react-component-taggers package poses a serious threat to users. Immediate action is required to mitigate risks, including uninstalling the package and securing sensitive information. Utilizing tools like Vulert can aid in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for react-component-taggers →

Share this vulnerability

FAQ

react-component-taggers is an npm package used for tagging and managing React components in development.

If you have the react-component-taggers package installed, your system may be compromised. Use tools like Vulert to check for vulnerabilities.

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

Currently, there is no patched version available. The best course of action is to remove the package entirely.

Vulert monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file, providing real-time insights.

How To Fix

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

npm uninstall react-component-taggers

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