Which versions of reayctjs are malicious?

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

How do I remediate reayctjs if I installed it?

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

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

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

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

Malicious package

reayctjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7378

Immediate action

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

npm uninstall reayctjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

e872f2bee20f61c3f0f8d4e3e046a3f6edfc8be32d6731d3fdd4367dde0bcb32

ab6062be928fe97dcbd33f5054ff92ac557a8e7ba660df3391545782a7d5925b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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