Which versions of xzvbailsx are malicious?

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

How do I remediate xzvbailsx if I installed it?

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

If xzvbailsx was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is xzvbailsx part of a known attack campaign?

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

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for xzvbailsx (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging xzvbailsx across your stack and pipelines.

Malicious package

xzvbailsxnpm

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

MAL-2026-16279

Immediate action

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

npm uninstall xzvbailsx

What this malware does

package.json declares the dependency libsignal with source github:tenka-san/libsignal-node, an unpinned GitHub ref with no commit SHA, tag, or integrity hash. On npm install, npm fetches whatever HEAD of that repository currently points at and executes any lifecycle scripts (preinstall/install/postinstall) it contains on the installer's machine. The referenced GitHub account is a personal repository unrelated to the WhiskeySockets/Baileys upstream that this package forks. Provenance is further obscured by an identity mismatch: the package is published as xzvbailsx but README/examples describe it as @XzV-RxVz/xbails, and the repository field points to Telegram handles (t.me/JustRxVz, t.me/XzV_ExpzC) rather than a source repository.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

ac9176da252791a96b93c24e702c2245fb96d9655cdf9f31d61e9bc3e0c21528

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for xzvbailsx (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging xzvbailsx across your stack and pipelines.
If you installed it — respond
Remove xzvbailsx 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 xzvbailsx was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks xzvbailsx before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. xzvbailsx 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-020177

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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