Which versions of reauctjs are malicious?

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

How do I remediate reauctjs if I installed it?

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

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

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

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

Malicious package

reauctjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7376

Immediate action

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

npm uninstall reauctjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

802d3ed8d6e24da77fa75dd62652b9c73d9c09c144f49addc6a2c8a3b55d8a83

25b02f5ff5f6ab2bc37c555f0aef490d534856f97fcaf2594fe731dca7492c5c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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