Critical Malicious Code Vulnerability in @daffadeveloper/baileys Package

@daffadeveloper/baileys Updated 02 Mar 2026

Summary

02/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1117: Malicious code in @daffadeveloper/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 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 @daffadeveloper/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 identified to contain malicious code that compromises the security of any system it is installed on.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the @daffadeveloper/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 origin of this vulnerability is linked to a malicious actor who has exploited the package to gain control over user systems. The ramifications are severe, as it poses a risk of data breaches and unauthorized actions on affected systems.

How To Fix

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

npm uninstall @daffadeveloper/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, ensure that you do not run any applications that depend on the @daffadeveloper/baileys package until the issue is resolved. Regularly monitor your system for any unusual activity and consider using security tools to scan for potential threats.

Conclusion

The @daffadeveloper/baileys package contains a critical vulnerability due to embedded malicious code, posing significant risks to any system it is installed on. Immediate action is required to remove the package and secure sensitive information. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for @daffadeveloper/baileys →

Share this vulnerability

FAQ

Immediately remove the package 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.

Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in your open-source packages.

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

Exercise caution. Review the security of other packages from the same developer and consider using alternatives that have a better security track record.

How To Fix

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

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