Critical Malicious Code Vulnerability in @chatest/baileys Package

@chatest/baileys Updated 13 Oct 2026

Summary

13/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17850: Malicious code in @chatest/baileys (npm). Affected versions are not published. 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 @chatest/baileys package is an npm library designed for building WhatsApp clients. It provides various functionalities for interacting with the WhatsApp API, making it a popular choice among developers. However, this package has been identified as containing malicious code, posing significant security risks to any system where it is installed.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the @chatest/baileys package. Any system running this package is considered fully compromised, potentially allowing unauthorized access to sensitive information such as secrets and keys. The malicious code can lead to severe ramifications, including data breaches and loss of control over the affected system.

How To Fix

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

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

There are no effective workarounds for this vulnerability other than removing the package and securing your system. It is essential to monitor your system for any signs of compromise after the removal.

Conclusion

The @chatest/baileys package has been identified as containing malicious code, posing serious security risks. Immediate action is required to remove the package and secure any compromised systems. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for @chatest/baileys →

Share this vulnerability

FAQ

You should uninstall the package immediately and rotate any sensitive information stored on the affected system.

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.

Failure to address this vulnerability can lead to unauthorized access to sensitive data, potential data breaches, and loss of control over your system.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, and keep your packages updated to the latest secure versions.

Caution is advised. Always review the code and check for vulnerabilities in any package before installation, regardless of the author.

How To Fix

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

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