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

@saazkira/baileys Updated 30 Sep 2026

Summary

30/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17377: Malicious code in @saazkira/baileys (npm). Affects @saazkira/baileys versions 2.1.6 – 2.1.9. 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 @saazkira/baileys package is a fork of the Baileys WhatsApp Web library, designed to facilitate interactions with the WhatsApp Web API. It is part of a larger family of similar packages that have been identified as potentially malicious. These packages are known for their ability to manipulate WhatsApp sessions and perform unauthorized actions on behalf of the user.

Vulnerability Detail

The vulnerability arises from a malicious code injection that occurs when the package connects to the WhatsApp socket layer. This code executes an unauthorized 'w:mex' FOLLOW query using the user's authenticated session, subscribing the victim's account to attacker-controlled channels without consent. The targeted JIDs are obfuscated using various techniques, making detection difficult. This vulnerability does not exfiltrate user credentials or execute arbitrary code but exploits the user's session for malicious purposes.

How To Fix

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

npm uninstall @saazkira/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, users can avoid using the @saazkira/baileys package until a secure version is confirmed. Additionally, consider using alternative libraries that do not exhibit these vulnerabilities.

Conclusion

The @saazkira/baileys package contains a significant vulnerability that allows malicious actors to exploit users' authenticated sessions for unauthorized actions. It is crucial for developers to update to the latest version and utilize tools like Vulert for ongoing monitoring to ensure the security of their applications.

See every vulnerability recorded for @saazkira/baileys →

Share this vulnerability

FAQ

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

You can use Vulert to monitor your application for vulnerabilities. By analyzing your package-lock.json file, Vulert can alert you in real-time about any open-source vulnerabilities.

The main consequence is unauthorized subscription to channels, which could lead to unwanted notifications and potential privacy concerns.

Yes, regularly update your dependencies and monitor them using tools like Vulert to catch vulnerabilities early.

Immediately update the package to the latest version using 'npm install @saazkira/baileys@latest' to mitigate the risk.

How To Fix

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

npm uninstall @saazkira/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