Which versions of rzeactjs are malicious?

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

How do I remediate rzeactjs if I installed it?

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

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

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

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

Malicious package

rzeactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7417

Immediate action

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

npm uninstall rzeactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

07686d9e4d195199536b27bf7b8d3c3051f80350e2901615ca36dd97095842d2

dfc1cb6c65d4d1f6d37fec927ee1c253d4b537505eaeb6452563c2bed97da972

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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