Critical Malicious Code Vulnerability in baileys-dtz Package

baileys-dtz Updated 06 Feb 2026

Summary

03/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-672: Malicious code in baileys-dtz (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 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 baileys-dtz package is an npm library designed for specific functionalities within JavaScript applications. It is widely used for its ease of integration and utility in various projects. However, it has been found to contain malicious code that poses significant security risks to systems using this package.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the baileys-dtz package. This code can compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code has been confirmed by security sources, indicating that systems running this package should be considered fully compromised.

How To Fix

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

npm uninstall baileys-dtz

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, if immediate removal of the package is not feasible, consider isolating the affected system from the network to prevent further compromise. However, this is only a temporary measure and does not guarantee complete security.

Conclusion

The baileys-dtz package contains malicious code that poses serious security risks. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for baileys-dtz →

Share this vulnerability

FAQ

The baileys-dtz package is an npm library used in JavaScript applications for specific functionalities, but it has been compromised with malicious code.

If you have the baileys-dtz package installed, your system is likely affected. You can use tools like Vulert to monitor and alert for vulnerabilities in your software.

Immediately remove the baileys-dtz package and rotate any sensitive information stored on the affected system.

Currently, there is no patched version available. The best course of action is to remove the package entirely.

Vulert monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file, providing real-time insights without requiring code access.

How To Fix

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

npm uninstall baileys-dtz

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