Which versions of react-native-fetch are malicious?

The following npm versions of react-native-fetch are flagged malicious: 2.0.1, 2.0.2. Treat any of these as compromised.

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

react-native-fetch 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-fetch — how do I know if it already compromised me?

If react-native-fetch was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

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

Yes — react-native-fetch is associated with the GHSA-887c-pvp7-c2fw 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-fetch across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for react-native-fetch (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-native-fetch across your stack and pipelines.

Malicious package

react-native-fetchnpm

Malicious code in react-native-fetch (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190997

Immediate action

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

npm uninstall react-native-fetch

What this malware does

The package react-native-fetch 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

2.0.12.0.2

Indicators of compromise (SHA-256)

db7a9dc0ac9009379058c4a3de0db9b5f82dd51419e446a11b23d4f57d56a9bb

b96159f9c8f74a56ea1f03322401befd0e090840e21dff7d1cc37db649e8cd58

b1ae7205486cfd8ba705501ccad3e4ce9cfa1f34d5ca4b74a5c65591af0e9a74

8466952d4ef9966e1d5c38cff6c23ecf8eefe56afb3a1bbaaa56d77fb35bbf76

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for react-native-fetch (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-native-fetch across your stack and pipelines.
If you installed it — respond
react-native-fetch 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-fetch was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks react-native-fetch before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

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

Campaign

GHSA-887c-pvp7-c2fw

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks react-native-fetch-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