Critical Malicious Code Vulnerability in zeroz-baileys Package

zeroz-baileys Updated 19 Oct 2026

Summary

19/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17933: Malicious code in zeroz-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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The zeroz-baileys package is an npm library that is used for various functionalities in JavaScript applications. It is designed to facilitate certain tasks within the Node.js ecosystem. However, this package has been identified to contain malicious code, posing a significant security risk to any system that has it installed.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the zeroz-baileys package. This code can compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The implications of this vulnerability are severe, as it can lead to full control of the affected system by an external entity. Users are advised to treat any system with this package as fully compromised.

How To Fix

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

npm uninstall zeroz-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 recommended to monitor your system for any unusual activity following the removal.

Conclusion

The zeroz-baileys package poses a critical security risk due to the presence of malicious code. Immediate action is required to remove the package and secure any sensitive information. Users should remain vigilant and consider using tools like Vulert to monitor their applications for vulnerabilities.

See every vulnerability recorded for zeroz-baileys →

Share this vulnerability

FAQ

The zeroz-baileys package is an npm library used in JavaScript applications, but it has been found to contain malicious code.

If you have the zeroz-baileys package installed, your system is considered compromised. It is advisable to remove the package immediately.

After removal, rotate all secrets and keys stored on the affected computer from a different, secure machine.

No, there is no patch available for this package. The only solution is to uninstall it.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.

How To Fix

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

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