Which versions of reacxtjs are malicious?

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

How do I remediate reacxtjs if I installed it?

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

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

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

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

Malicious package

reacxtjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7369

Immediate action

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

npm uninstall reacxtjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

c8a4f39e0ec4e377c6bdcfba0218bd6979bd56bd1b962ba795d5c428ae3dafd9

d49cf3da5a7bba5224635186889319a01836f7ccb621cc738f3af4d341c7272b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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