# MAL-2026-13931: Malicious code in @dreamguyxeon/libsignal-node (npm)


- **Type:** Malicious package
- **Package:** `@dreamguyxeon/libsignal-node` (npm)
- **Published:** 10 Aug 2026
- **Also known as:** GHSA-x3rc-jwjw-pwv6

## What is MAL-2026-13931?

MAL-2026-13931 is a malicious package in @dreamguyxeon/libsignal-node, published on 10 Aug 2026. 

### Official description

npm/@dreamguyxeon/libsignal-node has the same import-time supply-chain tampering as @dgxeon13/libsignal-node@1.0.0: on require it patches @whiskeysockets/baileys lib/Socket/newsletter.js with remote-controlled consentless WhatsApp newsletter auto-follow code (fetch DGXeon13/strings after 120s, silent FOLLOW). Used as the libsignal npm alias dependency from my-auto-follow@1.0.3. Related campaign OSV: MAL-2026-2252, MAL-2025-806. Tarball sha256: 41906336d7a9cbf416ca8ac3e01af4ffad13a1048cd306390734fa18a061ba8c.

Package is published as a Signal protocol implementation but its shipped code has no Signal functionality. index.js schedules install.js one second after require(). install.js locates the installer's @whiskeysockets/baileys module and overwrites lib/Socket/newsletter.js with an embedded replacement, drops a marker file at baileys/node_modules/.cache containing 'Iove' to make the tamper persistent and idempotent, and forces process.exit(0) 20 seconds later, abruptly terminating the host process. The replacement newsletter.js fetches https://raw.githubusercontent.com/DGXeon13/strings/refs/heads/main/strings.json (a personal GitHub repo, mutable main branch) and iterates the returned IDs to call newsletterWMexQuery(id, QueryIds.FOLLOW), causing the installer's authenticated WhatsApp session to follow attacker-chosen channels. Because the injected file is a full rewrite of the dependency's source and the remote list is mutable and unauthenticated, the author retains the ability to change the JSON at any time to drive arbitrary newsletter operations on every installer's WhatsApp account, and could substitute more damaging behavior into the rewritten newsletter.js path.

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

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

## Sources

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

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