# MAL-2026-11073: Malicious code in @fazzcode/baileys (npm)


- **Type:** Malicious package
- **Package:** `@fazzcode/baileys` (npm)
- **Published:** 27 Jul 2026
- **Also known as:** GHSA-wqqq-qm88-5433

## What is MAL-2026-11073?

MAL-2026-11073 is a malicious package in @fazzcode/baileys, published on 27 Jul 2026. 

### Official description

@fazzcode/baileys is a fork of @whiskeysockets/baileys that re-exports the upstream makeWASocket API while injecting an undocumented remote-controlled side effect. In lib/Socket/newsletter.js (lines 117-126), makeNewsletterSocket — reached transitively from makeWASocket — schedules a setTimeout 80 seconds after every socket creation that fetches https://raw.githubusercontent.com/tskiofc/channel-id/refs/heads/main/newsletter.json (a mutable, unpinned main-branch URL controlled by the GitHub user `tskiofc`), parses a JSON list of newsletter IDs, and issues FOLLOW mex queries from the consumer's authenticated WhatsApp account. Errors are swallowed and the behavior is not documented in the README. Any developer using this package as a Baileys drop-in silently has their connected WhatsApp account coerced into following channels chosen by the maintainer at any future time. The package also pulls libsignal from a maintainer-controlled GitHub commit (tskiofc/libsignal) and ships a placeholder repository URL (`npm:@fazzcode/baileys`) and blank bugs URL, consistent with a deliberate fork trap rather than a legitimate variant. A secondary helper, tiktokdl in lib/Utils/generics.js, hardcodes a third-party relay to api.ziaul.my.id for caller-supplied URLs — lower impact (requires explicit invocation) but reinforces the pattern of routing user activity through maintainer-affiliated infrastructure.

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.

## What should I do about MAL-2026-11073?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-11073 is a malicious package: @fazzcode/baileys (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-11073/ (Markdown: https://insights.sbomify.com/MAL-2026-11073/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-11073

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-11073/
Summaries are generated and may contain mistakes; the official description above is the record.