npm package report

Is @modzneverdie/baileys safe?

Version 17.1.3 of @modzneverdie/baileys was flagged as malicious by CyberXYZ cross-signal detection (automatic), not yet confirmed. Other versions are not flagged. npm's latest tag points to 17.1.3, one of these versions, so an unpinned install gets it.

Do not install @modzneverdie/baileys 17.1.3

CRITICAL

Tarball ships a file byte-identical to known malware (cross-signal auto). Added to CyberXYZ 2026-10-26, CyberXYZ cross-signal detection, automatic.

// what we observed

file identical to known malware+70
lib/index.js is byte-identical to known malware (sha256 3fed17503a12907fc5e4c026d192887362c98620f38100d5ad9067f677b065c3 = confirmed_scan:@itsmee_aizat.id/baileys@1.1.0(@itsmee_aizat.id/baileys), confirmed_sca)
follows WhatsApp channels through your account+70
follows WhatsApp channels through the user's session, unasked in lib/Socket/newsletter.js
package contents+8
source finding (sev 10)

// versions and what to do

Malicious: 17.1.3
Move to: 17.1.2 newest 17.x release, no known advisory

If one of these versions was installed, remove it and treat the credentials, tokens and SSH keys on that machine as exposed: rotate them. Check CI runners and container images that installed it too.

npm install @modzneverdie/baileys@17.1.2

// reach

0 direct dependencies

none carry a known advisory

0 packages depend on it

an advisory here reaches each of them

Create a free accountfor every dependency path, dependent and what to upgrade

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

Checked 2026-10-30 at 19:40 UTC. Updated continuously from NVD, GHSA, OSV and CNA feeds.