Which versions of react-native-websocket are malicious?

The following npm versions of react-native-websocket are flagged malicious: 1.0.3, 1.0.4. Treat any of these as compromised.

How do I remediate react-native-websocket if I installed it?

react-native-websocket is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed react-native-websocket — how do I know if it already compromised me?

If react-native-websocket was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is react-native-websocket part of a known attack campaign?

Yes — react-native-websocket is associated with the GHSA-mjmr-345m-q4j2 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find react-native-websocket across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for react-native-websocket (2 malicious versions).

Malicious package

react-native-websocketnpm

Advisory published Nov 24, 2025Updated Nov 26, 2025

react-native-websocket is a confirmed malicious npm package (MAL-2025-191006) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.3, 1.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in react-native-websocket (npm)

MAL-2025-191006

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall react-native-websocket

What this malware does

The package react-native-websocket was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

2 flagged

1.0.31.0.4

Indicators of compromise (SHA-256)

bc8e0788790181b5410794ec84d6605fd128b64b79ff4e36dac5cccb9917dfa4

f48d8c015af60bd1c1cbe48b9005dbbde091d8abc3763d25544d978b8b133094

9d65f76328737c1b1f2fe38fa9fc65e0d36931a1a440a4e33e3723133c1d0690

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for react-native-websocket (2 malicious versions).
If you installed it — respond
react-native-websocket is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If react-native-websocket was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. react-native-websocket on npm has been identified as a malicious package (versions 1.0.3, 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-mjmr-345m-q4j2

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks react-native-websocket-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database