Which versions of rezactjs are malicious?

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

How do I remediate rezactjs if I installed it?

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

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

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

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

Malicious package

rezactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7392

Immediate action

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

npm uninstall rezactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

a8606602b6fbbb8c70edf7542b25d9981dc7c3bb74f8ec6b9468a7752b1b7fda

e9e63eb1a021782962b091b10eb5e013dc636976780374abf3237a9e7e7b8587

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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