Which versions of reaactjs are malicious?

The following npm versions of reaactjs are flagged malicious: 1.1.2, 1.1.4, 8.7.6. Treat any of these as compromised.

How do I remediate reaactjs if I installed it?

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

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

Yes — reaactjs is associated with the RLMA-2026-05249, RLUA-2026-06407 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 reaactjs across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for reaactjs (3 malicious versions).

Malicious package

reaactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

reaactjs is a confirmed malicious npm package (MAL-2026-7358) that executes malicious code on install (malicious versions 1.1.2, 1.1.4, 8.7.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in reaactjs (npm)

MAL-2026-7358

Immediate action

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

npm uninstall reaactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

d49f30af47fdd04f75dc8c6d476eaff734b172d2b22d4cf3108c41723992560c

a4cf2baeb464efac074f50e26794621c52140731984a26c7077b27a9d7035b8e

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05249RLUA-2026-06407

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks reaactjs-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