Malicious Code Detected in f34th3r-react-components: A Critical Security Alert

f34th3r-react-components Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20122: Malicious code in f34th3r-react-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 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 f34th3r-react-components package is a library designed for building user interfaces in React applications. It provides a set of reusable components that enhance the development process by offering pre-built functionalities. However, this package has been identified as containing malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the f34th3r-react-components package originates from the inclusion of malicious code that can compromise the integrity and security of applications using this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious nature of this vulnerability makes it critical for developers to take immediate action to protect their applications.

How To Fix

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

npm uninstall f34th3r-react-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 f34th3r-react-components package from your project until a secure version is available. Use the following command to uninstall the package: npm uninstall f34th3r-react-components.

Conclusion

The discovery of malicious code in the f34th3r-react-components package highlights the importance of maintaining secure dependencies in software development. Developers are urged to take immediate action by updating or removing the affected package to safeguard their applications.

See every vulnerability recorded for f34th3r-react-components →

Share this vulnerability

FAQ

It is a library for building user interfaces in React applications, offering reusable components.

The specific nature of the malicious code has not been disclosed, but it poses significant security risks.

You can use Vulert's playground at Vulert Scanner to check for vulnerabilities without needing to sign up.

Consider removing the package from your project as a temporary measure until a secure version is released.

Vulert uses package-lock.json to monitor and alert in real-time for open-source vulnerabilities in your software.

How To Fix

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

npm uninstall f34th3r-react-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