Which versions of reacytjs are malicious?

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

How do I remediate reacytjs if I installed it?

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

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

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

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

Malicious package

reacytjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7370

Immediate action

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

npm uninstall reacytjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

7b5c34a1821b697ba2e693e12e82dc543266ceba8ad83140510a4b738421187c

3e52d226e38dc3d9696b2ad8105c4b849615b8996afdefe67c5c96f5151e7c26

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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