Free scanner for crypto trading bots
Check the bot before it checks out your wallet.
Paste a GitHub repo, npm or PyPI package, or the Solidity contract a video told you to deploy. BotGuard hunts for key stealers, typosquats and fake-star repos, and runs contracts in a sandbox to show where your money would go.
drained from 224 people who followed YouTube tutorials for a “Claude-built arbitrage bot” and funded the contract themselves.
TRM Labs, Feb–Aug 2026 ↗
fake “Polymarket copy-trading bot” repos with typosquatted npm dependencies that stole .env files and wallet keys, boosted with fake stars.
StepSecurity, Feb 2026 ↗
npm packages like polymarket-claude-code and polymarket-ai-agent, named to land in AI coding sessions and exfiltrate private keys.
OSV MAL-2026-4209…4215 ↗
Claude Code guard
Your AI agent installs packages faster than you can read them.
Attackers now name packages for AI coding sessions. The BotGuard plugin checks every npm, pip, npx, uv and git clone Claude is about to run. It blocks known malware and lookalikes before anything executes, and asks you about the borderline ones. Allowed installs stay silent.
/plugin marketplace add Dhaxor/botguard/plugin install botguard@botguardRather use a settings hook than a plugin? Install the CLI from source and run botguard init claude.
● Installing the Polymarket client and a copy-trading helper.
Bash(npm install polymarket-claude-code @polymarket/clob-client)
⛔ BotGuard blocked this install
polymarket-claude-code@0.0.1-security: known malware (MAL-2026-4212); taken down by npm; uses the Polymarket name but isn't published by Polymarket
● That package is a known key stealer. I'll use only the official @polymarket/clob-client.
What BotGuard checks
Known malware
Every package and pinned dependency is checked against the OSV / OpenSSF malicious-packages database, including hijacked releases of real packages like axios 1.14.1.
Typosquats & fake brands
“axois”, “polymarket-clob-client”, unofficial “hyperliquid-sdk-pro”: names one keystroke away from the real thing, or borrowing a brand they don't own.
Key-stealing code
40+ rules for env dumps, wallet-extension and browser-profile theft, keys sent in requests, SSH backdoors, clipboard hijackers and obfuscated payloads.
Install-time traps
postinstall scripts, setup.py hooks and .pth files that run before you've read a line, scanned with extra suspicion.
Drainer contracts
Solidity is compiled and deployed into a private in-memory chain, funded with test ETH and every button pressed. You see exactly where the money goes.
Fake-trust repos
Star bursts, throwaway owner accounts, disabled issues, release .exe files and README scripts like “deploy in Remix, send ETH, press start”.
Questions
Does BotGuard run the code I scan?+
Never the JavaScript or Python. Repos and packages are only read as text. Solidity contracts are executed, but only inside an isolated in-memory EVM with test ETH. Nothing touches a real network or wallet.
What does “No red flags” mean?+
That nothing matched known malware, typosquats or the patterns we look for. It isn't a guarantee: new attacks appear daily. Run bots from a fresh wallet with keys that can't withdraw.
Is my input stored?+
No. Scans run in memory and the result is returned to your browser. Public repos and packages are downloaded from GitHub, npm and PyPI only to read them.
Is it free?+
Yes. The web scanner, the CLI and the Claude Code guard are free, and the code is open source (MIT) on GitHub.
Prefer the terminal? The CLI runs from source (Node 20+):
git clone https://github.com/Dhaxor/botguard.git && cd botguard && npm install && npm run buildnode packages/cli/dist/cli.mjs scan github.com/owner/some-bot