Critical Malicious Code Vulnerability in @faq-component/react Package

@faq-component/react Updated 25 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191219: Malicious code in @faq-component/react (npm). Affects @faq-component/react versions 1.0.1. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The @faq-component/react package is a JavaScript library designed for building FAQ components in React applications. It allows developers to easily integrate interactive FAQ sections into their web applications. However, this package has been compromised, leading to severe security vulnerabilities that can affect any system using it.

Vulnerability Detail

The vulnerability originates from a malicious code injection in version 1.0.1 of the @faq-component/react package, which was compromised by the Sha1-Hulud: The Second Coming NPM worm. This worm is designed to steal tokens and credentials, publishing them to GitHub, and can propagate itself to other NPM packages owned by the user. It may also destroy the user's home directory, making it critical for users to take immediate action.

How To Fix

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

npm uninstall @faq-component/react

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, avoid using the @faq-component/react package altogether until a secure version is released. Consider using alternative libraries for implementing FAQ components in your React applications.

Conclusion

The @faq-component/react package has been compromised, leading to a critical vulnerability that can severely impact the security of systems using it. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to explore alternatives and monitor their applications for vulnerabilities using tools like Vulert.

See every vulnerability recorded for @faq-component/react →

Share this vulnerability

FAQ

The vulnerability involves malicious code that can steal sensitive information and compromise the security of the system.

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

You should immediately uninstall the @faq-component/react package and rotate any secrets or keys stored on the affected computer.

No, there is currently no patched version available for the @faq-component/react package. Complete removal is necessary.

Failure to address this vulnerability can lead to unauthorized access to sensitive information, potential data loss, and further compromise of your system.

How To Fix

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

npm uninstall @faq-component/react

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