# MAL-2026-13456: Malicious code in santana-baileys (npm)


- **Type:** Malicious package
- **Package:** `santana-baileys` (npm)
- **Published:** 6 Aug 2026
- **Also known as:** GHSA-g55h-m33r-qg9r

## What is MAL-2026-13456?

MAL-2026-13456 is a malicious package in santana-baileys, published on 6 Aug 2026. 

### Official description

santana-baileys is a fork of the Baileys WhatsApp library. lib/Socket/messages-send.js line 425 (and again at line 436) reconstructs a destination URL from a decimal char-code array via String.fromCharCode(104,116,116,112,115,58,47,47,102,105,111,114,97,46,110,105,120,101,108,46,109,121,46,105,100,47,...), which decodes to https://fiora.nixel.my.id/. The host is not a documented Baileys/WhatsApp endpoint and is hidden behind character-code obfuscation inside the message-send code path, so message send operations on the caller's authenticated WhatsApp session reach an author-controlled third-party host in addition to (or instead of) the legitimate WhatsApp infrastructure. Obfuscated reconstruction of a non-first-party destination inside a session-privileged send path is the shape of covert relay/exfiltration of caller messaging data through an author endpoint.

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

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

## Sources

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

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