Malicious Code Detected in react-nodes Package - Version 4.0.1

react-nodes Updated 02 Oct 2025

Summary

26/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6327: Malicious code in react-nodes (npm). Affects react-nodes versions 4.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 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-nodes package is an npm library designed to facilitate the creation and management of React nodes in web applications. It provides developers with tools to streamline their workflow and enhance the functionality of their React components. However, version 4.0.1 of this package has been identified as malicious, executing harmful commands that could compromise the security of applications using it.

Vulnerability Detail

The vulnerability in the react-nodes package arises from its malicious behavior, where it executes commands that can lead to unauthorized actions within the host environment. This behavior poses significant risks, including data breaches, unauthorized access to sensitive information, and potential system compromise. The malicious code was identified by the OpenSSF Package Analysis project, which flagged the package due to its harmful actions.

How To Fix

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

npm uninstall react-nodes

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 measure, you can remove the react-nodes package from your project until a secure version is available. Use the following command to uninstall the package: npm uninstall react-nodes. This will help mitigate any potential risks associated with the malicious code.

Conclusion

The react-nodes package version 4.0.1 has been flagged as malicious due to its harmful behavior. It is crucial for developers using this package to take immediate action by updating to a secure version or uninstalling the package to protect their applications from potential threats.

See every vulnerability recorded for react-nodes →

Share this vulnerability

FAQ

react-nodes is an npm library that helps developers manage React nodes in their applications.

A malicious package contains code that performs harmful actions, such as executing unauthorized commands or compromising system security.

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.

You should immediately update the package to the latest version or uninstall it to prevent any potential security risks.

Vulert uses the package-lock.json file to monitor your dependencies and alert you in real-time about any open-source vulnerabilities.

How To Fix

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

npm uninstall react-nodes

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