Which versions of rieactjs are malicious?

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

How do I remediate rieactjs if I installed it?

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

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

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

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

Malicious package

rieactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7396

Immediate action

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

npm uninstall rieactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

f474b403bc86ed675ca751af631fd9b03b5b01688d7d572b871136c09d4a4187

e8c4c764140bbc19c413956f1488672a9858ebf85d18d2653bd46d0e15be209a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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