zeppeliorg-wbails

Ecosystem: npm

Downloads:

Vulnerabilities from the last (months)
  • 0CriticalAffects 0 versions
  • 0HighAffects 0 versions
  • 0MediumAffects 0 versions
  • 0ModerateAffects 0 versions
  • 0LowAffects 0 versions
Severity distribution (all time)
0vulnerabilities
  • Critical0 (0.0%)
  • High0 (0.0%)
  • Medium0 (0.0%)
  • Moderate0 (0.0%)
  • Low0 (0.0%)

Monthly breakdown

  • 0 vulnerabilities
    • Critical: 0
    • High: 0
    • Medium: 0
    • Moderate: 0
    • Low: 0

Vulnerabilities (1)

Known vulnerabilities affecting zeppeliorg-wbails, based on data from OSV.

Vulnerabilities affecting zeppeliorg-wbails
IDSeveritySummaryAffected versionsPublishedSource
MAL-2026-18925UnknownMalicious code in @zeppeliorg/wbails (npm)@zeppeliorg/wbails is a fork of the Baileys WhatsApp Web library that silently subscribes the installer's own WhatsApp account to WhatsApp Channels chosen by the publisher. When the socket connects, code in lib/Socket/newsletter.js sends the WhatsApp w:mex FOLLOW query for the channel ID(s) 120363330344810280@newsletter, 120363349140729983@newsletter, 120363400738305381@newsletter, 120363410018949906@newsletter, 120363410614416828@newsletter, 120363418691561888@newsletter and 7 more (stored as base64 strings), using the victim's authenticated session and without telling them. Same behaviour as
  • all
OSV (opens in a new tab)
  • MAL-2026-18925Unknown
    Malicious code in @zeppeliorg/wbails (npm)
    • all

    @zeppeliorg/wbails is a fork of the Baileys WhatsApp Web library that silently subscribes the installer's own WhatsApp account to WhatsApp Channels chosen by the publisher. When the socket connects, code in lib/Socket/newsletter.js sends the WhatsApp w:mex FOLLOW query for the channel ID(s) 120363330344810280@newsletter, 120363349140729983@newsletter, 120363400738305381@newsletter, 120363410018949906@newsletter, 120363410614416828@newsletter, 120363418691561888@newsletter and 7 more (stored as base64 strings), using the victim's authenticated session and without telling them. Same behaviour as

Showing 1-1 of 1 vulnerabilities