Which versions of rheactjs are malicious?

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

How do I remediate rheactjs if I installed it?

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

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

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

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

Malicious package

rheactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7395

Immediate action

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

npm uninstall rheactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

3a21a1bac0dc237a049aa92aa5ba45ba00761e77e46ec97f24bcbdb7771bddd0

80cb964975a58be9532c8c6e99a0585fdc2b53f7646197fb11e81d3fa87205ff

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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