Covert Channel Subscription Vulnerability in @teamolduser/baileys Package

@teamolduser/baileys Updated 30 Sep 2026

Summary

30/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17380: Malicious code in @teamolduser/baileys (npm). Affects @teamolduser/baileys versions 9.10.1 – 9.7.3-beta.1. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The @teamolduser/baileys package is a fork of the Baileys WhatsApp Web library, designed to facilitate interactions with the WhatsApp platform. It allows developers to create applications that can send and receive messages, manage contacts, and perform various other tasks on WhatsApp. However, this package has been identified as part of a larger family of malicious forks that introduce vulnerabilities, specifically by injecting covert actions into the WhatsApp socket layer.

Vulnerability Detail

The vulnerability arises from malicious code embedded within the @teamolduser/baileys package, which is part of a family of over 100 similar forks. This code executes an unauthorized FOLLOW query using the installer's authenticated WhatsApp session, subscribing the victim's account to attacker-controlled channels without consent. The target JIDs are obfuscated using various techniques, making it difficult for users to detect the malicious behavior. This vulnerability does not exfiltrate credentials or execute arbitrary code but exploits the user's session for unauthorized channel subscriptions.

How To Fix

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

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

Conclusion

The @teamolduser/baileys package has a significant vulnerability that allows unauthorized subscriptions to WhatsApp channels using the user's authenticated session. It is crucial for developers to update to a secure version and consider alternative libraries to mitigate risks.

See every vulnerability recorded for @teamolduser/baileys →

Share this vulnerability

FAQ

The vulnerability allows malicious code to subscribe users to unauthorized 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 any signup.

You should update the package to the latest secure version using npm install @teamolduser/baileys@latest.

No, this vulnerability does not exfiltrate credentials but exploits the user's session for unauthorized actions.

Yes, consider using other WhatsApp libraries that do not have known vulnerabilities.

How To Fix

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

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