Which versions of reacktjs are malicious?

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

How do I remediate reacktjs if I installed it?

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

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

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

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

Malicious package

reacktjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7362

Immediate action

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

npm uninstall reacktjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

4d709a5375e3a6284a3f96421e866655666e82a864d7d5f10df96b2307c66fc1

f1fb419dfd4902ec4e73374c2e8548bf9ad05917b7e39c5d503b3af3ea20274a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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