Which versions of cheaty-sync-bot are malicious?

The following npm versions of cheaty-sync-bot are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate cheaty-sync-bot if I installed it?

cheaty-sync-bot is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed cheaty-sync-bot — how do I know if it already compromised me?

If cheaty-sync-bot was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is cheaty-sync-bot part of a known attack campaign?

Yes — cheaty-sync-bot is associated with the IN-MAL-2026-003204 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find cheaty-sync-bot across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cheaty-sync-bot (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cheaty-sync-bot across your stack and pipelines.

Malicious package

cheaty-sync-botnpm

Malicious code in cheaty-sync-bot (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4518

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall cheaty-sync-bot

What this malware does

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.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

45b192c71c59ccca1d9cc720372bd29f39eae8b5da4d572cd1e8312d6b57d6b4

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cheaty-sync-bot (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cheaty-sync-bot across your stack and pipelines.
If you installed it — respond
cheaty-sync-bot is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If cheaty-sync-bot was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks cheaty-sync-bot before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. cheaty-sync-bot on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-003204

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks cheaty-sync-bot-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring