MAL-2026-4518 Malicious code in cheaty-sync-bot (npm)
Malicious package
Published
MAL-2026-4518 is a malicious package: cheaty-sync-bot (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-4518/ (Markdown: https://insights.sbomify.com/MAL-2026-4518/index.md)
- Package
- cheaty-sync-bot
- Registry
- npm
What is MAL-2026-4518?
MAL-2026-4518 is a malicious package in cheaty-sync-bot, published on 19 May 2026.
Official description
cheaty-sync-bot ships a clipboard-sync CLI that hardcodes a single Telegram bot token (index.js:10) owned by the package author. There is no configuration path for installers to supply their own bot — every user of this tool connects to the same author-controlled relay. Two concrete harms result: (1) Silent-relay: clipboard contents (text and images) and installer chat identifiers flow through the author's Telegram bot, giving the author visibility into every installer's session via getUpdates polling. (2) Backdoor / remote code execution: incoming Telegram messages are interpolated into a PowerShell command (
powershell -Command "Set-Clipboard -Value \"${escapedText}\"") at index.js:31-34 and passed to exec(). The escaping only replaces double quotes with backtick-quotes; PowerShell metacharacters such as backticks, $(...) subexpressions, and newlines are not sanitized, so anyone holding the bot token (the author, or anyone who obtains it) can send a crafted message to any installer running the CLI and achieve arbitrary command execution on the Windows host.What should I do about MAL-2026-4518?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.