Malicious Code Injection in xvinleys Package: Covert Subscription to WhatsApp Channels

xvinleys Updated 30 Sep 2026

Summary

30/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17409: Malicious code in xvinleys (npm). Affects xvinleys versions 1.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 xvinleys package is part of a larger family of npm packages that are forks of the Baileys WhatsApp Web library. These packages are designed to interact with the WhatsApp API, allowing developers to create applications that can send and receive messages. However, the xvinleys package has been identified as having malicious code that exploits the user's authenticated WhatsApp session to subscribe them to unwanted channels without their consent.

Vulnerability Detail

The vulnerability in the xvinleys package arises from its ability to inject malicious code into the WhatsApp socket layer. Upon connection, the package issues an authenticated 'w:mex' FOLLOW query to attacker-controlled WhatsApp Channel/Newsletter JIDs, using the victim's own WhatsApp session. This action occurs silently, without the user's knowledge, effectively subscribing them to channels they did not intend to join. The obfuscation techniques used to hide the target JIDs include plain string literals, base64 encoding, and runtime reconstruction, making it difficult for users to identify the malicious behavior through casual source review.

How To Fix

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

npm uninstall xvinleys

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 xvinleys package from your project by executing the following command: npm uninstall xvinleys. This will prevent any malicious code from executing until a safe version is released.

Conclusion

The xvinleys package contains a serious vulnerability that allows for the covert subscription of users to unwanted WhatsApp channels. It is crucial for users to take immediate action by updating or uninstalling the package to protect their accounts. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for xvinleys →

Share this vulnerability

FAQ

xvinleys is an npm package that is part of a family of forks of the Baileys WhatsApp Web library, designed for interacting with the WhatsApp API.

The vulnerability allows attackers to subscribe users to unwanted WhatsApp channels using their own authenticated session, without their consent.

You should update the package to a patched version or uninstall it to prevent any malicious actions.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just the package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

npm uninstall xvinleys

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