npm package report

Is @raffnotdev/baileys safe?

Version 1.0.0 of @raffnotdev/baileys was compromised (WhatsApp channel hijack (PhantomSub): follows publisher-chosen channels through the user's session). Other versions are not flagged as malicious. npm's latest tag points to 1.0.0, one of these versions, so an unpinned install gets it.

Do not install @raffnotdev/baileys 1.0.0

CRITICALanalyst verified

WhatsApp channel hijack (PhantomSub): follows publisher-chosen channels through the user's session. Added to CyberXYZ 2026-10-10, verified by a CyberXYZ analyst.

// what we observed

file identical to known malware+70
lib/Utils/index.js is byte-identical to known malware (sha256 72c6503827c82fc0b1b651f0039f9a159c7fec0259323963660748863eb7ac88 = confirmed_scan:@hanzofc/baileys@7.1.0(@hanzofc/baileys))
package contents+15
novel source finding (sev 10)
install script diff+20
preinstall appeared vs prior version (no network/exec in the script itself — corroborating only)

// versions and what to do

Malicious: 1.0.0
Move to: Pin a release that is not listed above: the latest tag points to one that is.

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.

// 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:37 UTC. Updated continuously from NVD, GHSA, OSV and CNA feeds.