Security audit
Security checks for vulnerabilities and agentic risk
This skill is a live Binance trading bot whose documented safety limits are incomplete or unenforced, so it needs careful review before use with real funds.
Treat this as a Review item, not a routine install. Use only Binance API keys with withdrawals disabled, IP restrictions, and limited funds. Do not run the cron example or live trading until you have verified or added real dry-run mode, confirmation gates, position caps, DCA scheduling, exchange filter validation, and stop-loss/take-profit behavior.
scripts/trader.py:137Documented Position, Take-Profit, and Stop-Loss Controls Are Not Enforced
scripts/trader.py:148DCA Interval Is Ignored, Allowing Purchases on Every Invocation
scripts/trader.py:160Unvalidated Configuration Values Flow into Market-Order Quantities
scripts/setup.sh:4Installer Fetches and Installs PyPI Artifacts Without Integrity Verification
The declared behavior understates or misstates materially risky functionality: the skill places live exchange orders while lacking clear permission declarations, and it claims risk controls and portfolio management features that static analysis indicates are not actually enforced. In a financial trading skill, this mismatch is especially dangerous because users may rely on nonexistent stop-loss, take-profit, or position-limit protections and suffer direct monetary loss from autonomous execution.
The markdown describes an autonomous trader and cron execution, but it does not prominently and early warn that using the skill can place real exchange orders on a recurring schedule with real funds. In a financial context, insufficient warning is dangerous because users may treat setup/run steps as informational or simulated and unknowingly enable unattended live trading.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
set -e
echo "=== Binance Spot Trader Setup ==="
pip install httpx==0.27.0 python-dotenv==1.0.1
echo "Done. Create .env with BINANCE_API_KEY, BINANCE_SECRET_KEY, and LLM_API_KEY"
The bot can place live MARKET buy and sell orders directly against a real Binance account based solely on programmatic signals, with no explicit user confirmation, dry-run default, or safety interlock. In a trading automation skill, this is especially dangerous because mistakes, prompt-driven misuse, bad configuration, or logic errors can immediately convert into irreversible financial loss.
The skill advertises and instructs use of environment secrets, file creation/logging, and network access to Binance and an LLM provider, but does not declare explicit tool scope or permissions. In an autonomous trading context, missing scope declarations materially increases the risk of unintended live trading, secret exposure, or other side effects because users and runtime policy cannot clearly constrain what the skill may do.
The activation language is broad enough to trigger on general requests about trading, automation, DCA, or building a bot, which can cause the skill to be invoked in contexts where the user did not intend live order execution. Because this skill can autonomously trade on a real exchange, overly loose matching raises the chance of high-risk actions being surfaced or run without sufficiently specific user intent.
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
- Start with tiny amounts ($50-100) and paper trade first
- Monitor actively during first 24 hours
- Set up Binance email alerts for all trades
- **API keys on disk** — secure your server (SSH keys only, firewall, chmod 600)
## References
This code accesses sensitive credentials via BINANCE_API_KEY and BINANCE_SECRET_KEY and sends an authenticated request to retrieve account data from Binance. There is no confirmation prompt, user-facing warning, or explanatory comment/docstring disclosing that private account information will be accessed over the network.
The script sends trading-derived data such as symbol, recent closes, volume trend, and RSI to a third-party API when USE_LLM is enabled. This is a network transmission of user/system-derived trading data, but the file provides no user-facing warning, prompt, or explanatory comment disclosing that market context from the user's trading workflow is shared externally.
The script transmits trading context to a third-party LLM endpoint, creating an external data flow outside Binance and the local system. In an autonomous trading bot, this increases exposure of proprietary strategy inputs and can create privacy, compliance, and operational risk if users are not informed or if future prompt changes include sensitive account details.
Reply ONLY a number."""
with httpx.Client(timeout=30) as c:
resp = c.post("https://api.anthropic.com/v1/messages",
headers={"x-api-key": LLM_API_KEY, "anthropic-version": "2023-06-01", "Content-Type": "application/json"},
json={"model": "claude-3-5-haiku-20241022", "max_tokens": 20, "messages": [{"role": "user", "content": prompt}]})
text = resp.json().get("content", [{}])[0].get("text", "0.5").strip()
No suspicious patterns detected.