Which versions of reatctjs are malicious?

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

How do I remediate reatctjs if I installed it?

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

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

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

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

Malicious package

reatctjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7375

Immediate action

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

npm uninstall reatctjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

bf21c2c7554951a1adcbd7755b19acaed3b897cc64f147c6310df94a5dbdd23d

44e8111ad7e4c2c439d821158c2009010dd1e0d276e56b6bd4f1a87677dbe030

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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