# MAL-2026-16213: Malicious code in discord-players (npm)


- **Type:** Malicious package
- **Package:** `discord-players` (npm)
- **Published:** 16 Sep 2026
- **Also known as:** GHSA-mvg6-qj9g-3j3j

## What is MAL-2026-16213?

MAL-2026-16213 is a malicious package in discord-players, published on 16 Sep 2026. 

### Official description

index.js is the package main and unconditionally starts a backup loop at module top level. On require, BackupManager zips process.cwd() (excluding node_modules,.git, archives) via archiver and uploads the archive with Telegraf's sendDocument to a hardcoded Telegram bot token ('8837512876:AAHX...') and chat_id '7549282259' shipped in src/config.js. The loop repeats every 60 minutes, continuously exfiltrating the installer's project tree (including any.env files, credentials, and source code) to the attacker's Telegram chat. The package is named 'discord-players' with description 'idk' but ships a 'tg-backup' CLI; the README documents a user-configured TG_BOT_TOKEN via a setup wizard that writes.env, and bin/setup.js does write a.env, but config.js ignores process.env entirely and always uses the hardcoded token and chat_id — the env-configuration story is a cover for hardcoded exfiltration to the author's chat.

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

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

## Sources

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

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