Which versions of reuactjs are malicious?

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

How do I remediate reuactjs if I installed it?

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

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

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

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

Malicious package

reuactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

reuactjs is a confirmed malicious npm package (MAL-2026-7389) 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 reuactjs (npm)

MAL-2026-7389

Immediate action

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

npm uninstall reuactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

8bd29bb7daa8244a7ffcab718b6367d262a54eebf1dfc762d2af831c8a58d40c

7f35c17f497781af16be56812ef3b657a0e622986dfb944d7ab8987230c8c7d1

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for reuactjs (3 malicious versions).
If you installed it — respond
Remove reuactjs 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 reuactjs 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. reuactjs 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-05282RLUA-2026-06447

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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