Critical Malicious Code Vulnerability in xmd-baileys Package

xmd-baileys Updated 16 Oct 2026

Summary

16/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17892: Malicious code in xmd-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 xmd-baileys package is an npm library designed for specific functionalities within JavaScript applications. However, it has been identified as containing malicious code that compromises the security of any system where it is installed. This vulnerability poses a significant risk to users, as it can lead to unauthorized access and control over affected systems.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the xmd-baileys package. This code can fully compromise any computer that has the package installed, allowing attackers to gain access to sensitive information such as secrets and keys. The ramifications are severe, as the compromised system may be controlled by an external entity, making it difficult to ensure complete removal of the malicious software even after uninstalling the package.

How To Fix

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

npm uninstall xmd-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, users should ensure that the xmd-baileys package is uninstalled from their systems. Use the following command to remove the package: npm uninstall xmd-baileys. Additionally, consider using tools like Vulert to monitor your application for vulnerabilities in real-time.

Conclusion

The xmd-baileys package poses a critical security risk due to the presence of malicious code. Users are strongly advised to uninstall the package immediately and take necessary precautions to secure their systems. Regular monitoring for vulnerabilities is essential to maintain software security.

See every vulnerability recorded for xmd-baileys →

Share this vulnerability

FAQ

Immediately uninstall the xmd-baileys package and rotate any sensitive information stored on your system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

Currently, there is no patch available. The best course of action is to uninstall the package and secure your system.

Failure to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential control by malicious actors.

While many npm packages are safe, it's essential to monitor and review packages for vulnerabilities regularly. Tools like Vulert can help with this.

How To Fix

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

npm uninstall xmd-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