Malicious Code Injection in @lendkzn/xntaabail Package

@lendkzn/xntaabail Updated 30 Sep 2026

Summary

30/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17364: Malicious code in @lendkzn/xntaabail (npm). Affects @lendkzn/xntaabail versions 7.0.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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The @lendkzn/xntaabail package is part of a larger family of forks derived from the Baileys WhatsApp Web library. It is designed to facilitate interactions with the WhatsApp platform. However, this package has been identified as containing malicious code that exploits the user's authenticated WhatsApp session to subscribe them to unwanted channels without their consent.

Vulnerability Detail

The vulnerability stems 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. This action occurs silently, using the installer's own WhatsApp session, thereby subscribing the victim's account to channels they did not intend to join. The obfuscation techniques used to hide the target JIDs include plain string literals, base64 encoding, and dynamic fetching of target lists from remote sources, making detection difficult. While the malicious action does not exfiltrate credentials or execute arbitrary code, it does compromise user consent and privacy.

How To Fix

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

npm uninstall @lendkzn/xntaabail

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 temporary workaround, you can remove the @lendkzn/xntaabail package from your project to prevent any malicious actions. This can be done using the command: npm uninstall @lendkzn/xntaabail. Additionally, consider using alternative libraries that do not have known vulnerabilities.

Conclusion

The @lendkzn/xntaabail package contains a significant vulnerability that allows malicious actors to exploit users' authenticated WhatsApp sessions. It is crucial to take immediate action by updating or removing the package to safeguard user privacy and consent.

See every vulnerability recorded for @lendkzn/xntaabail →

Share this vulnerability

FAQ

The vulnerability involves malicious code that subscribes users to unwanted WhatsApp channels using their authenticated session.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

The primary risk is the unauthorized subscription of users to channels, which compromises user consent and privacy.

Regularly update your packages and utilize tools like Vulert to monitor for vulnerabilities in your dependencies.

If affected, uninstall the package immediately and monitor your WhatsApp account for any unauthorized activity.

How To Fix

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

npm uninstall @lendkzn/xntaabail

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