Critical Malicious Code Vulnerability in react-devtools-shared Package

react-devtools-shared Updated 30 Dec 2025

Summary

30/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192972: Malicious code in react-devtools-shared (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 react-devtools-shared package is a component of the React ecosystem, designed to facilitate debugging and profiling of React applications. It provides developers with tools to inspect and manipulate the React component tree, enhancing the development experience. However, this package has been compromised, leading to significant security concerns.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the react-devtools-shared package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code is classified under CWE-506, indicating that it contains embedded malicious code. The ramifications of this vulnerability are severe, as it may lead to data breaches and loss of control over the affected systems.

How To Fix

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

npm uninstall react-devtools-shared

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

Currently, the only effective workaround is to uninstall the react-devtools-shared package. You can do this by running the following command in your terminal: npm uninstall react-devtools-shared. This action should be taken as soon as possible to mitigate any potential damage.

Conclusion

The react-devtools-shared package has been identified as containing malicious code that poses a significant security risk. Immediate action is required to remove the package and secure any sensitive information. Regular monitoring for vulnerabilities using tools like Vulert is recommended to maintain the security of your applications.

See every vulnerability recorded for react-devtools-shared →

Share this vulnerability

FAQ

It is a package used in the React ecosystem for debugging and profiling React applications.

The malicious code can compromise your system, allowing unauthorized access to sensitive information.

You should immediately uninstall the package and rotate any sensitive information stored on your system.

As of now, there is no patch available. The best course of action is to uninstall the package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities without signup at the Vulert playground.

How To Fix

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

npm uninstall react-devtools-shared

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