Which versions of revactjs are malicious?

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

How do I remediate revactjs if I installed it?

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

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

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

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

Malicious package

revactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7390

Immediate action

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

npm uninstall revactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

27cc681949e823a3500b5dd46816d6a7db9ab9572c7a4c955a81c2f1b1e12c6f

cc5b1c0f1caa5664f383d6a87908a38f3a1d867f033f0e3f45c3efa6d4107551

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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