Which versions of regactjs are malicious?

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

How do I remediate regactjs if I installed it?

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

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

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

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

Malicious package

regactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7381

Immediate action

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

npm uninstall regactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

a2e70c446bf05b3a4577f46cbeb629634bb5d0e07793658ea59d69a1c008b22d

f359072c393c3b1a95abac63a34195bfb314273b67a788f2b4cdd9a8007b2d57

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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