Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Malicious code in zeroz-baileys (npm)

GHSA-fwfc-f4gp-qrcq

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm zeroz-baileys

    Affected
    every version
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

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

Source: amazon-inspector (7be2199641fd598bfa6c6a11fac2567fa0c50f3f55ae3a8e8cd9ecd6ec4bf20f) zeroz-baileys@1.0.1 appears to be a fork of the Baileys WhatsApp library. A static pattern matched on keyword co-occurrence in lib/Utils/messages-media.js (require('child_process'), https.request, hostname, POST) within a single file. This shape is expected for a media-handling utility in a WhatsApp library (media upload/download via HTTPS requests, optional native tool dispatch). Traced-code corroboration of installer-side harm was not established — no specific installer secret is named as read, and no non-first-party attacker-controlled destination is identified. Being a fork of a widely-used library, the package warrants human review to confirm whether the fork introduces covert behavior (e.g., using the installer's WhatsApp session for author-controlled actions) versus being a legitimate derivative.

Source: ghsa-malware…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from osv record MAL-2026-17933

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-fwfc-f4gp-qrcq

Advisory: Malicious code in zeroz-baileys (npm)
IDs: GHSA-fwfc-f4gp-qrcq
Record: https://patchnext.com/advisories/mal-2026-17933 (revision 1, source checked 30 Oct 2026, 06:15 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm zeroz-baileys: affected every version

## Suggested inspection (read-only)
- `npm ls zeroz-baileys --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on zeroz-baileys.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/MAL-2026-17933 (OSV record MAL-2026-17933 lists affected ranges: npm zeroz-baileys >=0)

Commands are suggestions: review each one before running it.

Loading voting…