npm package report

Is @teamqadeer1/baileys safe?

Versions 1.0.1 and 1.0.0 of @teamqadeer1/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 1.0.1, one of these versions, so an unpinned install gets it.

Do not install @teamqadeer1/baileys 1.0.1 or 1.0.0

CRITICAL

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

// what we observed

file identical to known malware+70
lib/Utils/index.js is byte-identical to known malware (sha256 307418601d92b67c5595b1ab389f3d1603d0f3ee2b5bb34ee73f6e6b0d9bc8ae = confirmed_scan:noxleyss@2.0.0(noxleyss), confirmed_scan:noxleyss@2.0.1(noxleyss), conf)
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: 1.0.1, 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:41 UTC. Updated continuously from NVD, GHSA, OSV and CNA feeds.