Critical Malicious Code Vulnerability in @aseppxyzz12/baileys Package

@aseppxyzz12/baileys Updated 09 Oct 2026

Summary

09/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17731: Malicious code in @aseppxyzz12/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 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 @aseppxyzz12/baileys package is an npm library designed for building WhatsApp clients. It provides developers with tools to interact with the WhatsApp API, enabling functionalities such as sending messages, managing contacts, and handling media. However, this package has been compromised, embedding malicious code that poses significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the @aseppxyzz12/baileys package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code has been confirmed by security researchers, and it is classified under CWE-506, indicating that it contains embedded malicious code. Users are advised to treat any system running this package as compromised.

How To Fix

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

npm uninstall @aseppxyzz12/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 workaround, it is recommended to avoid using the @aseppxyzz12/baileys package altogether. If your application relies on its functionality, consider looking for alternative packages that provide similar capabilities without the associated risks.

Conclusion

The @aseppxyzz12/baileys package has been identified as containing malicious code that compromises the security of any system using it. Immediate action is required to uninstall the package and secure any sensitive information. Regular monitoring of dependencies is essential to maintain application security.

See every vulnerability recorded for @aseppxyzz12/baileys →

Share this vulnerability

FAQ

Immediately uninstall the package and rotate any sensitive information stored on the affected system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.

Currently, there is no patched version available for the @aseppxyzz12/baileys package.

Failing to address this vulnerability could lead to unauthorized access to sensitive data and complete control of your system by malicious actors.

While many npm packages are safe, it is crucial to monitor and audit your dependencies regularly for vulnerabilities.

How To Fix

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

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