Critical Malicious Code Vulnerability in babel-plugin-react-pure-component

Summary

22/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-2067: Malicious code in babel-plugin-react-pure-component (npm). Affects babel-plugin-react-pure-component versions 0.1.6. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

babel-plugin-react-pure-component is an npm package designed to optimize React components by implementing pure component principles. This package is intended to enhance performance by preventing unnecessary re-renders. However, it has been found to contain malicious code that compromises the security of any system where it is installed.

Vulnerability Detail

The vulnerability stems from embedded malicious code within the babel-plugin-react-pure-component package, identified as GHSA-f9q8-fcvg-876p. 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 poses severe risks, as it can lead to data breaches and unauthorized control over the affected systems.

How To Fix

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

npm uninstall babel-plugin-react-pure-component

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

There are no specific workarounds to mitigate the risks associated with this vulnerability. The only recommended action is to uninstall the affected package and secure your system.

Conclusion

The discovery of malicious code within the babel-plugin-react-pure-component package poses a significant threat to users. Immediate action is required to uninstall the package and secure any sensitive information. Regular monitoring for vulnerabilities, such as through Vulert, can help prevent future incidents.

See every vulnerability recorded for babel-plugin-react-pure-component →

Share this vulnerability

FAQ

You should uninstall the package immediately using the command: npm uninstall babel-plugin-react-pure-component.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.

Keeping this package installed can lead to unauthorized access to sensitive information and full control of your system by malicious actors.

No, there is currently no patched version available for this package.

After uninstalling, you should rotate all secrets and keys stored on the affected computer from a different, secure system.

How To Fix

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

npm uninstall babel-plugin-react-pure-component

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