Which versions of react-native-forter are malicious?

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

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

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

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

Yes — react-native-forter is associated with the RLMA-2026-01811 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-forter across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for react-native-forter (version 1.0.0).

Malicious package

react-native-forternpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

react-native-forter is a confirmed malicious npm package (MAL-2026-2386) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in react-native-forter (npm)

MAL-2026-2386

Immediate action

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

npm uninstall react-native-forter

What this malware does

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

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

0e4728aff5f5caa8a8151a09f286f487edfa2ceb57a527671e3c15d13bda129c

ff4ae821a2636c10a3e19afaaf78823613bcedf143d91c79cbdec29f20b00654

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for react-native-forter (version 1.0.0).
If you installed it — respond
Remove react-native-forter 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-forter 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-forter on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01811

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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