Which versions of retactjs are malicious?

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

How do I remediate retactjs if I installed it?

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

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

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

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

Malicious package

retactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7388

Immediate action

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

npm uninstall retactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

7e04f597120edfe10fea2703687b954b2d27f4880621258c13294e196a653f71

2debe2fb069e9d2bd89ca7a70d3955ea4d34dbab09c2a6c8f04edf1e34dec77a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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