Malicious Code Detected in fbfr4 Package - Security Alert

fbfr4 Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20275: Malicious code in fbfr4 (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The fbfr4 package is an npm library that is utilized for various functionalities within JavaScript applications. It is designed to enhance development efficiency by providing reusable components. However, the package has been identified as containing malicious code, which poses significant security risks to applications that depend on it.

Vulnerability Detail

The vulnerability in the fbfr4 package stems from the inclusion of malicious code that can compromise the security of applications utilizing this package. This code may lead to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall fbfr4

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, consider replacing the fbfr4 package with an alternative library that provides similar functionality without the security risks. Ensure to review the security posture of any alternative packages before integration.

Conclusion

The fbfr4 package has been identified as containing malicious code, posing significant risks to applications that utilize it. Users are urged to take immediate action by updating or removing the package to safeguard their applications. Regular monitoring for updates and vulnerabilities is essential for maintaining security.

See every vulnerability recorded for fbfr4 →

Share this vulnerability

FAQ

The fbfr4 package is an npm library used in JavaScript applications for various functionalities, but it has been found to contain malicious code.

The malicious code can lead to unauthorized access, data breaches, and other security issues, putting your application and its users at risk.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json, Vulert can help identify if your application is affected by this vulnerability.

If an immediate update is not possible, consider removing the fbfr4 package and replacing it with a secure alternative until a patched version is available.

For more information on vulnerabilities and how to manage them, you can visit Vulert's website, which provides tools for monitoring and alerting on open-source vulnerabilities.

How To Fix

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

npm uninstall fbfr4

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