npm package report

Is @rakku-kun/baileys safe?

Versions 2.0.26, 2.0.24, 2.0.31 and 2.0.27 of @rakku-kun/baileys were flagged as malicious by CyberXYZ cross-signal detection (automatic), not yet confirmed. Other versions are not flagged. npm's latest tag points to 2.0.31, one of these versions, so an unpinned install gets it.

Do not install @rakku-kun/baileys 2.0.26, 2.0.24, 2.0.31 or 2.0.27

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

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: 2.0.26, 2.0.24, 2.0.31, 2.0.27
Move to: 2.0.23 newest 2.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 @rakku-kun/baileys@2.0.23

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