Which versions of vbails are malicious?

The following npm versions of vbails are flagged malicious: 0.0.10, 0.0.11. Treat any of these as compromised.

How do I remediate vbails if I installed it?

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

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

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

Search your lockfiles and build artifacts for vbails (2 malicious versions).

Malicious package

vbailsnpm

Advisory published Dec 1, 2025Updated Dec 2, 2025

vbails is a confirmed malicious npm package (MAL-2025-191599) that executes malicious code on install (malicious versions 0.0.10, 0.0.11). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vbails (npm)

MAL-2025-191599

Immediate action

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

npm uninstall vbails

What this malware does

The package vbails was found to contain malicious code.

Malicious versions

2 flagged

0.0.100.0.11

Indicators of compromise (SHA-256)

cc7f5da0dbe9909000eed14fceebfdf3d475bff9a5823a807ae517ba963b6ef9

a53e29fb2fb76cdb2684ae2d929ec8a17af80e96a5b42f7e0e49b5f46330481f

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for vbails (2 malicious versions).
If you installed it — respond
Remove vbails 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 vbails 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. vbails on npm has been identified as a malicious package (versions 0.0.10, 0.0.11 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05976

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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