Malicious Code Injection in @noxleyss/baileys: Covert Channel Subscription Vulnerability

@noxleyss/baileys Updated 30 Sep 2026

Summary

30/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17369: Malicious code in @noxleyss/baileys (npm). Affects @noxleyss/baileys versions 1.1.10. 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 @noxleyss/baileys package is a fork of the Baileys WhatsApp Web library, designed to facilitate interactions with the WhatsApp Web API. This package is part of a larger family of similar forks, all exhibiting a concerning vulnerability that allows for unauthorized channel subscriptions using the installer's authenticated WhatsApp session.

Vulnerability Detail

This vulnerability arises from malicious code embedded within the @noxleyss/baileys package, which injects a covert channel-subscription action into the WhatsApp socket layer. Upon connection, the code executes an authenticated 'w:mex' FOLLOW query targeting attacker-chosen WhatsApp Channel/Newsletter JIDs. This action subscribes the victim's account to channels without their consent, leveraging their own authenticated session. The obfuscation techniques used to hide the target JIDs include string literals, base64 encoding, and dynamic fetching from remote sources, making detection challenging. While the malicious action does not exfiltrate credentials or execute arbitrary code, it compromises user privacy and consent.

How To Fix

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

npm uninstall @noxleyss/baileys

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, consider removing the @noxleyss/baileys package from your project until a secure version is released. You can do this by executing: 'npm uninstall @noxleyss/baileys'. Additionally, monitor your application for any unauthorized subscriptions to WhatsApp channels.

Conclusion

The @noxleyss/baileys package poses a significant risk due to its malicious code that subscribes users to channels without consent. It is crucial to update the package to a secure version and monitor applications for any unauthorized activities. Utilizing tools like Vulert can aid in identifying vulnerabilities in your projects.

See every vulnerability recorded for @noxleyss/baileys →

Share this vulnerability

FAQ

The package contains malicious code that subscribes users to WhatsApp channels without their consent.

It injects a covert action into the WhatsApp socket layer that executes an unauthorized FOLLOW query using the user's authenticated session.

The risks include unauthorized channel subscriptions, potential privacy violations, and misuse of the user's WhatsApp account.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

As a temporary measure, uninstall the package and monitor for any unauthorized activity related to WhatsApp subscriptions.

How To Fix

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

npm uninstall @noxleyss/baileys

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