# MAL-2026-13390: Malicious code in @xsat10/baileys-xsat (npm)


- **Type:** Malicious package
- **Package:** `@xsat10/baileys-xsat` (npm)
- **Published:** 6 Aug 2026
- **Also known as:** GHSA-fj9m-r2qx-cc39

## What is MAL-2026-13390?

MAL-2026-13390 is a malicious package in @xsat10/baileys-xsat, published on 6 Aug 2026. 

### Official description

Package is a fork of the Baileys WhatsApp Web library. Static keyword co-occurrence patterns matched on lib/Utils/generics.js (ping/GET references) and lib/Utils/messages-media.js (require('child_process') alongside POST/GET/hostname tokens), but these are consistent with Baileys' normal media upload/download paths and connectivity checks rather than a traced exfiltration flow. The concern is fork provenance: Baileys forks have previously been used to wire covert side effects (e.g. auto-follow of author-controlled newsletters, install counters) into the main exported API using the consumer's authenticated WhatsApp session. No specific installer-side data read and non-first-party destination pair has been identified in the code paths matched.

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

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

## Sources

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

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