Malicious code in @alannxd/baileys (npm)
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.
Affected packages
npm @alannxd/baileys
- Affected
- >= 6.2.8, <= 6.2.8>= 6.2.7, <= 6.2.7>= 6.1.7, <= 6.1.7>= 6.1.6, <= 6.1.6>= 6.1.4, <= 6.1.4>= 6.1.3, <= 6.1.3>= 6.1.2, <= 6.1.2>= 6.1.1, <= 6.1.1>= 6.1.0, <= 6.1.0>= 6.0.9, <= 6.0.9>= 6.0.6, <= 6.0.6>= 6.0.5, <= 6.0.5>= 6.0.4, <= 6.0.4>= 6.0.3, <= 6.0.3>= 6.0.2, <= 6.0.2>= 6.0.1, <= 6.0.1>= 6.0.0, <= 6.0.0>= 5.0.6, <= 5.0.6>= 5.0.5, <= 5.0.5>= 4.0.4, <= 4.0.4>= 4.0.5, <= 4.0.5>= 4.0.3, <= 4.0.3>= 3.0.3, <= 3.0.3>= 3.0.0, <= 3.0.0>= 2.1.4, <= 2.1.4>= 2.1.3, <= 2.1.3>= 2.1.2, <= 2.1.2
- Fixed in
- no fixed version recorded
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record MAL-2026-18120 lists affected ranges: npm @alannxd/baileys >=6.2.8 =6.2.7 =6.1.7 =6.1.6 =6.1.4 =6.1.3 =6.1.2 =6.1.1 =6.1.0 =6.0.9 =6.0.6 =6.0.5 =6.0.4 =6.0.3 =6.0.2 =6.0.1 =6.0.0 =5.0.6 =5.0.5 =4.0.4 =4.0.5 =4.0.3 =3.0.3 =3.0.0 =2.1.4 <=2.1.4,…
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
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 (8d2dd15da8d647385c59765df516101c97dbd343f01574a204a87b8cdaeaef3c) This is a fork of the Baileys WhatsApp library. On every `require('@alannxd/baileys')`, the package's main entry (`lib/index.js`) performs an unconditional HTTPS GET to `https://raw.githubusercontent.com/alannzxd/xclient/refs/heads/main/information.json` on a mutable branch of the author's personal GitHub repo and prints one string from the response via `console.log`. The response body is only logged — it is not passed to `eval`/`exec`/`Function`/`require` — so this is a covert usage phone-home (leaks installer IP + User-Agent + import-time signal to the author on each load) rather than a remote-code-execution channel. Separately, `package.json` declares `"libsignal": "npm:@alannxd/libsignal-node@latest"`, aliasing the well-known `libsignal` import specifier to an author-scoped package tracked at `latest`; every…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from osv record MAL-2026-18120
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-7345-fjw8-x55w Advisory: Malicious code in @alannxd/baileys (npm) IDs: GHSA-7345-fjw8-x55w Record: https://patchnext.com/advisories/mal-2026-18120 (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 @alannxd/baileys: affected >= 6.2.8, <= 6.2.8; >= 6.2.7, <= 6.2.7; >= 6.1.7, <= 6.1.7; >= 6.1.6, <= 6.1.6; >= 6.1.4, <= 6.1.4; >= 6.1.3, <= 6.1.3; >= 6.1.2, <= 6.1.2; >= 6.1.1, <= 6.1.1; >= 6.1.0, <= 6.1.0; >= 6.0.9, <= 6.0.9; >= 6.0.6, <= 6.0.6; >= 6.0.5, <= 6.0.5; >= 6.0.4, <= 6.0.4; >= 6.0.3, <= 6.0.3; >= 6.0.2, <= 6.0.2; >= 6.0.1, <= 6.0.1; >= 6.0.0, <= 6.0.0; >= 5.0.6, <= 5.0.6; >= 5.0.5, <= 5.0.5; >= 4.0.4, <= 4.0.4; >= 4.0.5, <= 4.0.5; >= 4.0.3, <= 4.0.3; >= 3.0.3, <= 3.0.3; >= 3.0.0, <= 3.0.0; >= 2.1.4, <= 2.1.4; >= 2.1.3, <= 2.1.3; >= 2.1.2, <= 2.1.2 ## Suggested inspection (read-only) - `npm ls @alannxd/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 @alannxd/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-18120 (OSV record MAL-2026-18120 lists affected ranges: npm @alannxd/baileys >=6.2.8 =6.2.7 =6.1.7 =6.1.6 =6.1.4 =6.1.3 =6.1.2 =6.1.1 =6.1.0 =6.0.9 =6.0.6 =6.0.5 =6.0.4 =6.0.3 =6.0.2 =6.0.1 =6.0.0 =5.0.6 =5.0.5 =4.0.4 =4.0.5 =4.0.3 =3.0.3 =3.0.0 =2.1.4 <=2.1.4,…) Commands are suggestions: review each one before running it.
Loading voting…