ChoiGPT Binance Trading Bot
WarnAudited by ClawScan on May 11, 2026.
Overview
This appears to be a real Binance futures trading bot, but it can trade automatically with sensitive API keys and can send account context to an undeclared Gemini AI endpoint.
Install only if you understand it is a live automated futures trading bot. Test with Binance testnet or very small limits first, use a dedicated no-withdrawal API key, explicitly review whether Gemini/Google AI calls are acceptable, and make sure you know how to stop the bot and revoke credentials.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If configured with trading-enabled Binance API keys, the bot may open or manage leveraged futures positions automatically, which can cause financial loss.
The bot can execute trades automatically when a signal is detected and auto-trading is enabled. The artifacts do not show a per-trade human approval step before real futures orders.
if analysis.signal and AUTO_TRADE_ENABLED:
sig = analysis.signal
logger.info(f"🚀 [SCALP] {symbol} 신호! {sig.direction} 확신도:{sig.confidence:.0%}")
self._execute_trade(symbol, analysis)Use testnet first, require manual confirmation if possible, set strict position and daily-loss limits, and only use Binance API keys with trading permissions needed for this bot and no withdrawal permission.
A Binance key with broad permissions could allow account trading activity; a Telegram token/chat ID can expose bot notifications to the configured chat.
The skill requires sensitive Binance and Telegram credentials. This is expected for the stated bot, but registry metadata says no required env vars or primary credential, so users may underestimate the credential boundary.
"BINANCE_API_KEY" ... "required": true "BINANCE_SECRET_KEY" ... "required": true "TELEGRAM_BOT_TOKEN" ... "required": true "TELEGRAM_CHAT_ID" ... "required": true
Create a dedicated Binance API key with no withdrawal permission, use IP allowlisting where possible, keep Telegram credentials private, and rotate any key that may have been exposed.
Trading account details and chat content may leave the local environment and be processed by a third-party AI provider without the user clearly expecting that from the registry metadata.
The analyzer builds prompts containing real account context such as balance, available funds, positions, PnL, and recent trades, then posts them to Google Gemini. The manifest discloses Binance and Telegram settings but not Google/Gemini configuration, and the code attempts to use a hardcoded fallback API key.
GEMINI_API_URL = "https://generativelanguage.googleapis.com/v1beta/models/{model}:generateContent?key={key}"
...
GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY", "AIzaSyCaXIU9NTdcU0QPe7jLsSM0rQF8b4JD6xA")
...
ctx_lines.append(f"잔고: ${bal:.2f} USDT (가용: ${avail:.2f})")
...
resp = requests.post(url, json=payload, timeout=15)Make Gemini use explicit and opt-in, declare GOOGLE_API_KEY in metadata, remove the hardcoded fallback key, and redact or minimize account details sent to external AI services.
If deployed with Docker, the bot may continue scanning and trading until the user explicitly stops the container or disables auto-trading.
The included Docker configuration is designed to keep the bot running and preserve state/log data. That is purpose-aligned for a trading bot, but important because it can keep operating after a crash or host restart.
restart: always volumes: - ./logs:/app/logs - ./data:/app/data - ./reports:/app/reports ... command: python run_bot.py
Only enable restart behavior after testing, document stop procedures, monitor logs and open positions, and avoid leaving live trading credentials active in unattended environments.