Advisory

MAL-2026-17846

Also known as: GHSA-qh6w-wgpq-j344

Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.

Summary

Malicious code in @yudzxml/baileys (npm)

Details

---
_-= Per source details. Do not edit below this line.=-_

Source: amazon-inspector (629ff06ada2390b75e4ba41304b30289746455bba454c455d04d7743f6998974)
This package is a fork of the Baileys WhatsApp Web library. a static rule matched on keyword co-occurrence in lib/Utils/messages-media.js: require('child_process'), require('os'), require('http')/require('https'), and POST/GET/fetch( calls, with the only cited literal URL being https://mmg.whatsapp.net (WhatsApp's own media server, which is the expected destination for a Baileys media utility). The evidence quotes do not name any non-first-party attacker endpoint, do not show environment-variable scraping, and do not show reads of installer-secret paths (~/.ssh, ~/.aws, ~/.npmrc, browser stores). The primitive co-occurrence in messages-media.js is the shape you would expect from a legitimate WhatsApp media upload/download implementation (child_process for ffmpeg/thumbnail generation, http/https/fetch for WhatsApp media endpoints, os for tmpdir). Because this is a fork of a widely used upstream library, and forks are a common vehicle for covert modifications (e.g., undocumented actions using the caller's WhatsApp session), a reviewer should diff this fork against upstream Baileys to confirm messages-media.js only talks to mmg.whatsapp.net/WhatsApp infrastructure, and that no other file in the package performs credential harvest, undocumented auto-follow/subscribe, or exfiltration using the caller's session. Without corroborating evidence of installer harm, keyword co-occurrence alone is not sufficient to publish a block.

Source: ghsa-malware (96357918fec8e046fe049ec94c614ab988e412532ace70beeb64d737533c3a30)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Severity

Not rated by the source.

Dates

Published
2026-10-12 16:31 UTC
Modified
2026-10-29 14:30 UTC

Affected packages and fixes

@yudzxml/baileys

npm · All systems

Affected

  • introduced 0 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: OpenSSF Malicious Packages · Apache-2.0

Sources & licences