Which versions of raeactjs are malicious?

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

How do I remediate raeactjs if I installed it?

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

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

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

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

Malicious package

raeactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7354

Immediate action

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

npm uninstall raeactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

c12bbe796518345824ad3ad0cc1a425db7272722f5fcfb78aa0b6d941e931451

231524935298191f984c7c45366b92f7f68b5cfc6a4c50c44c33d01bdfc25472

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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