Malicious Code Detected in mfe-react-bridge: Version 99.0.1 Compromised

mfe-react-bridge Updated 02 Oct 2025

Summary

16/05/2025
CRITICAL
No i
Critical
Not published

MAL-2025-3865: Malicious code in mfe-react-bridge (npm). Affects mfe-react-bridge versions 99.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 'mfe-react-bridge' package is a JavaScript library used in React applications to facilitate communication between micro-frontends. It is designed to enhance modularity and improve the user experience by allowing different parts of an application to be developed and deployed independently. However, version 99.0.1 has been flagged for malicious activity, raising concerns about its security and integrity.

Vulnerability Detail

The vulnerability in 'mfe-react-bridge' stems from its ability to communicate with a domain linked to malicious activities. This behavior indicates that the package may execute harmful commands, potentially compromising the security of applications that utilize it. The OpenSSF Package Analysis project identified this issue, highlighting the risks associated with using this specific version of the package.

How To Fix

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

npm uninstall mfe-react-bridge

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 removing the 'mfe-react-bridge' package from your project until a secure version is released. You can do this by running the command: npm uninstall mfe-react-bridge.

Conclusion

The 'mfe-react-bridge' package version 99.0.1 has been identified as malicious, posing significant security risks to applications that utilize it. It is crucial to update or remove the package to safeguard your application. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.

See every vulnerability recorded for mfe-react-bridge →

Share this vulnerability

FAQ

The package communicates with a domain associated with malicious activity and may execute harmful commands.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

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

Utilize tools like Vulert to monitor your package-lock.json file for real-time alerts on vulnerabilities.

Regularly audit your dependencies and use tools that can alert you to vulnerabilities as they arise.

How To Fix

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

npm uninstall mfe-react-bridge

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