Which versions of xzvbailey are malicious?

The following npm versions of xzvbailey are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate xzvbailey if I installed it?

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

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

Yes — xzvbailey is associated with the IN-MAL-2026-020176 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 xzvbailey across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for xzvbailey (version 1.0.0).

Malicious package

xzvbaileynpm

Advisory published Sep 18, 2026Updated Sep 18, 2026

xzvbailey is a confirmed malicious npm package (MAL-2026-16278) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in xzvbailey (npm)

MAL-2026-16278

Immediate action

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

npm uninstall xzvbailey

What this malware does

package.json declares the libsignal dependency as github:tenka-san/libsignal-node, a non-registry source pointing at a personal GitHub account with no tag or commit SHA. On npm install, npm fetches whatever the default branch's HEAD points to at that moment and runs any lifecycle scripts inside the cloned repo, so the owner of that account controls code that executes on the installer's machine. The account is unrelated to the upstream Baileys/libsignal publishers, and the package's own metadata is inconsistent (homepage and repository fields point at a Telegram URL while the bug tracker points at a different GitHub org, pou-code/Baileys), which is consistent with a repackaged Baileys lure rather than a legitimate fork.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

f961ec09baa139430fb2b04c3fef5350f16f659c8de585787a26f3c8535fca38

Detection & response playbook

Malicious package

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

Campaign

IN-MAL-2026-020176

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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