Which versions of vvvv4234 are malicious?

The following npm versions of vvvv4234 are flagged malicious: 1.0.0, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, 1.0.9, 1.0.10, 1.0.11, 1.0.12, 1.0.13, 1.0.14. Treat any of these as compromised.

How do I remediate vvvv4234 if I installed it?

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

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

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

Search your lockfiles and build artifacts for vvvv4234 (14 malicious versions).

Malicious package

vvvv4234npm

Advisory published Mar 18, 2026Updated Mar 23, 2026

vvvv4234 is a confirmed malicious npm package (MAL-2026-1873) that executes malicious code on install (malicious versions 1.0.0, 1.0.2, 1.0.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vvvv4234 (npm)

MAL-2026-1873

Immediate action

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

npm uninstall vvvv4234

What this malware does

The package vvvv4234 was found to contain malicious code.

Malicious versions

14 flagged

1.0.01.0.21.0.31.0.41.0.51.0.61.0.71.0.81.0.91.0.101.0.111.0.121.0.131.0.14

Indicators of compromise (SHA-256)

91a78d83d3036a7b983c87c27b59b9d2a7f2268763e339e7d9043579534edf17

b3fcc59e0dc323432a0f7e6f7fd19cad27a4a9811b9f3614906a6943c48a882b

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for vvvv4234 (14 malicious versions).
If you installed it — respond
Remove vvvv4234 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 vvvv4234 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. vvvv4234 on npm has been identified as a malicious package (versions 1.0.0, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, and 6 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01645

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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