Which versions of rveactjs are malicious?

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

How do I remediate rveactjs if I installed it?

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

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

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

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

Malicious package

rveactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7413

Immediate action

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

npm uninstall rveactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

32e5f5d5c41be1fb96b29bdb4098910ea76ebd6b39407e42565194d5bcb6ff43

9535e902ced15121526558606950ec11d7287dd2501ba13f4ddd81520eca7931

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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