Which versions of rreactjs are malicious?

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

How do I remediate rreactjs if I installed it?

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

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

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

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

Malicious package

rreactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7409

Immediate action

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

npm uninstall rreactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

43d1125a5579388617bfb2d289f63699a6215304af78d025bc416ad3d435df9d

349957720b6238cb339474d3d47b2a512af142996c67aaad0eca4f6de411dd40

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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