Which versions of reacrtjs are malicious?

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

How do I remediate reacrtjs if I installed it?

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

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

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

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

Malicious package

reacrtjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7364

Immediate action

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

npm uninstall reacrtjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

0756bcd9efabf6edfd1437cd5623d022b440a86e42b0e729cdeab3796dee4b92

2414d7ae795bcf0bdbe2b82b60bfd4f9d2d27ebf68b5974ad2d6c151619c2588

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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