# MAL-2026-17850: Malicious code in @chatest/baileys (npm)


- **Type:** Malicious package
- **Package:** `@chatest/baileys` (npm)
- **Published:** 13 Oct 2026
- **Also known as:** GHSA-c2gc-jwcq-w8r3

## What is MAL-2026-17850?

MAL-2026-17850 is a malicious package in @chatest/baileys, published on 13 Oct 2026. 

### Official description

The package.json of @chatest/baileys@4.4.0 declares the `libsignal` dependency as `github:chatunitycenter/libsignal-node` with no commit SHA, tag, or semver pin. On `npm install`, this resolves to whatever bytes are at the default branch HEAD of that external GitHub repository at the moment of installation, including any lifecycle scripts contained in them. The dependency is actively consumed via `require("libsignal")` in `lib/Signal/libsignal.js`, so it is part of the runtime tree and loaded on module import as well. Whoever controls the referenced GitHub repository controls code that runs on every installer's machine, unpinned and integrity-unchecked. The package also exhibits a scope/branding mismatch: it is published as `@chatest/baileys` but its `homepage` and `repository.url` both point at `@chatunity/baileys`, and the README banner brands the module as `ChatUnity Baileys`.

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-17850?

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-17850 is a malicious package: @chatest/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-17850/ (Markdown: https://insights.sbomify.com/MAL-2026-17850/index.md)
```

## Sources

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

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