Covert Channel Subscription Vulnerability in xzvexpzcbailey Package

xzvexpzcbailey Updated 30 Sep 2026

Summary

30/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17412: Malicious code in xzvexpzcbailey (npm). Affects xzvexpzcbailey versions 1.0.0 – 2.5.0. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The xzvexpzcbailey package is a part of a large family of forks derived from the Baileys WhatsApp Web library. It is designed to interact with the WhatsApp socket layer, enabling users to send and receive messages. However, this package has been identified to contain malicious code that exploits the user's authenticated WhatsApp session.

Vulnerability Detail

The vulnerability arises from the package's ability to inject a covert channel-subscription action into the WhatsApp socket layer. Upon connection, the malicious code executes an authenticated 'w:mex' FOLLOW query against attacker-controlled WhatsApp Channel/Newsletter JIDs, using the user's own session. This results in the victim's account being silently subscribed to channels without their consent. The obfuscation techniques used to hide the target JIDs include string literals, base64 encoding, and runtime reconstruction, making it difficult for users to detect the malicious behavior.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall xzvexpzcbailey

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a workaround, consider removing the xzvexpzcbailey package from your project entirely until a secure version is confirmed. You can do this by executing: npm uninstall xzvexpzcbailey.

Conclusion

The xzvexpzcbailey package contains a serious vulnerability that allows attackers to exploit users' authenticated WhatsApp sessions for unauthorized channel subscriptions. It is crucial to update or remove the package to mitigate risks associated with this vulnerability.

See every vulnerability recorded for xzvexpzcbailey →

Share this vulnerability

FAQ

xzvexpzcbailey is a fork of the Baileys WhatsApp Web library that allows interaction with WhatsApp's messaging services.

The vulnerability allows attackers to subscribe your account to channels without your consent, potentially leading to unwanted messages and privacy concerns.

You may notice unexpected subscriptions to channels or newsletters that you did not join, as well as unusual activity in your WhatsApp account.

Yes, Vulert can monitor your package-lock.json file for open-source vulnerabilities in real-time, alerting you to any issues, including this one.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall xzvexpzcbailey

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback