Which versions of reacetjs are malicious?

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

How do I remediate reacetjs if I installed it?

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

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

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

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

Malicious package

reacetjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7360

Immediate action

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

npm uninstall reacetjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

e8d13eb5e2f7f6863e632d8af3fd2795a19aaccc46de9ea58f4c80ac64887b9d

bd4993c2c2cb280ec35b5c332d15b2c97be28bea1cb334539dcdf54b9385f4de

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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