Which versions of rewactjs are malicious?

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

How do I remediate rewactjs if I installed it?

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

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

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

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

Malicious package

rewactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7391

Immediate action

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

npm uninstall rewactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

61d60734005bced052d22f0f337c81304ba0b0e891fc6168396760a691dff94f

b9a6e40323a55e2c3d7b8d4c0f0c4ff3c72bb4d19c4e2100f576af182f6eeb51

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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