Which versions of reacvtjs are malicious?

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

How do I remediate reacvtjs if I installed it?

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

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

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

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

Malicious package

reacvtjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7368

Immediate action

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

npm uninstall reacvtjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

f72cf3fdcd5bc98c447cf24ef1979e114d23c47ed2d5ba7dffbf0b1498355451

873f75218bf37e3ddfe2e576eff408ff9f6743d97295db985e62437e07004613

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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