cheaty-sync-bot
Always-on clipboard sync between Telegram and your Computer.
This report shows the evidence for cheaty-sync-bot@1.0.0, the only known version.
OpenSSF/OSV Malicious Advisory
imported 4mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-4518 confirms this npm version as malicious.
Advisory
MAL-2026-4518
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in cheaty-sync-bot (npm)
Details
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.
References
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to cheaty-sync-bot@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing cheaty-sync-bot@1.0.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.