Which versions of reacptjs are malicious?

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

How do I remediate reacptjs if I installed it?

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

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

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

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

Malicious package

reacptjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7363

Immediate action

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

npm uninstall reacptjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

4fc117e42107dbac8527b7625544e3239718f5367841db56d4d63936037f7363

179dcf1b8a5cf77759ff2524b90a31e715d896908416d03e25577605472ffb8c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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