bingx-copytrade-spot
Fail
Audited by Snyk on Apr 22, 2026
Risk Level: HIGH
Full Analysis
HIGH W007: Insecure credential handling detected in skill instructions.
- Insecure credential handling detected (high risk: 0.90). The skill requires passing an API key and secretKey into the provided fetchSigned function (which inserts the API key into request headers and uses the secret to compute HMAC signatures), so an agent that executes or materializes those calls would need to handle the secret and could end up outputting it verbatim — the prompt does not mandate secure, out-of-band secret provisioning (e.g., environment variables) and constrains the function so the LLM may be tempted to embed credentials directly.
MEDIUM W009: Direct money access capability detected (payment gateways, crypto, banking).
- Direct money access detected (high risk: 1.00). The skill is explicitly a trading integration for BingX copy-trade spot. It includes authenticated, HMAC-SHA256-signed API calls and a POST endpoint (/openApi/copyTrading/v1/spot/trader/sellOrder) whose purpose is to place sell orders (close positions). The Quick Reference, code samples, and Agent Interaction Rules explicitly describe executing a sell operation on production (with CONFIRM) — i.e., the skill's primary function is to execute financial transactions on an exchange. This is a specific tool to move money/assets (market/spot trades), not a generic capability.
Issues (2)
W007
HIGHInsecure credential handling detected in skill instructions.
W009
MEDIUMDirect money access capability detected (payment gateways, crypto, banking).
Audit Metadata