Which versions of rleactjs are malicious?

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

How do I remediate rleactjs if I installed it?

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

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

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

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

Malicious package

rleactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7399

Immediate action

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

npm uninstall rleactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

c766fa9c97de28519dfc425ee7ef65053d95cfbdc1693e4d07a51cb8d3432538

54e3db2de4ae59ce1c06c7c3794314a1157eacb04009c6a5f80e3ed45692ac4b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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