Which versions of react-native-httpapi are malicious?

The following npm versions of react-native-httpapi are flagged malicious: 3.1.4. Treat any of these as compromised.

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

Remove react-native-httpapi from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

If react-native-httpapi 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-httpapi part of a known attack campaign?

Yes — react-native-httpapi is associated with the GHSA-qp23-qjc6-hrj3, RLMA-2025-05136, RLUA-2026-01529 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-httpapi 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-httpapi (version 3.1.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-native-httpapi across your stack and pipelines.

Malicious package

react-native-httpapinpm

react-native-httpapi is a confirmed malicious npm package (MAL-2025-45764) that executes malicious code on install (malicious version 3.1.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in react-native-httpapi (npm)

MAL-2025-45764

Immediate action

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

npm uninstall react-native-httpapi

What this malware does

The package communicates with a domain associated with malicious activity.

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.

Malicious versions

1 flagged

3.1.4

Indicators of compromise (SHA-256)

872a61b5247749d233711d5fe71d6da937fd301c6cfe4317b41b6f69f4566000

0e5bf2eb04e6d86bbe3d5f45bd2568f8f579b50ed9d37e5c5d2178c9f8a8dc14

cbeab030e6f0b494855aeb0794ba89ad44aab10b4389c9846403292628abd6ff

173fb1e81e329644ad85502ec7e80667f7dded54fbbd6cbef2837b5189c39cd5

1a72175f83db0acc9fc3b56fe7f5dcb7fafa408731d79cab51fa9af88b1e931a

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for react-native-httpapi (version 3.1.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-native-httpapi across your stack and pipelines.
If you installed it — respond
Remove react-native-httpapi from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If react-native-httpapi 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-httpapi 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-httpapi on npm has been identified as a malicious package (version 3.1.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-qp23-qjc6-hrj3RLMA-2025-05136RLUA-2026-01529

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks react-native-httpapi-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database