Critical Malicious Code Vulnerability in react-native-websocket Package

react-native-websocket Updated 25 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191006: Malicious code in react-native-websocket (npm). Affects react-native-websocket versions 1.0.3 – 1.0.4. 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-native-websocket package is a popular library used in React Native applications to facilitate WebSocket communication. It allows developers to easily implement real-time features in their applications. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users and their systems.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the react-native-websocket package. This code can compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code has been confirmed by multiple sources, including Amazon Inspector and GHSA malware reports, indicating that systems running this package should be considered fully compromised.

How To Fix

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

npm uninstall react-native-websocket

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, you may consider using an alternative package for WebSocket communication in your React Native applications until the issue with react-native-websocket is resolved. Some alternatives include 'socket.io-client' or 'ws'.

Conclusion

The discovery of malicious code in the react-native-websocket package poses a serious threat to users and their systems. Immediate action is required to uninstall the package and secure sensitive information. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for react-native-websocket →

Share this vulnerability

FAQ

You should immediately uninstall the package and rotate any secrets or keys stored on the affected system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities. Visit Vulert Scanner to check your application without any signup.

Failing to address this vulnerability could lead to unauthorized access to sensitive data, system compromise, and potential data breaches.

Currently, there is no patched version available. It is recommended to remove the package until a fix is released.

You can use tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.

How To Fix

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

npm uninstall react-native-websocket

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