T08 · Insecure Dependencies
- Location
SKILL.md:6- Finding
Unpinned Privileged Third-Party Trading Dependency
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This crypto trading skill is transparent about its purpose, but it needs Review because it installs an unpinned trading CLI and can use exchange API keys for immediate financial actions.
Review this carefully before installing. Use sandbox mode for testing, prefer read-only API keys for account or market queries, enable trading permissions only when needed, disable withdrawals and transfers, and confirm every order or cancellation immediately before execution.
SKILL.md:6Unpinned Privileged Third-Party Trading Dependency
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
5. **ISO8601 datetimes** (e.g., `"2025-01-01T00:00:00Z"`) are auto-converted to milliseconds.
6. **API keys** must be configured via environment variables (e.g., `BINANCE_APIKEY`, `BINANCE_SECRET`) or the config file. If a private method fails due to missing credentials, instruct the user to set them up.
7. **Derivatives symbols** use the format `"BASE/QUOTE:SETTLE"` — e.g., `"BTC/USDT:USDT"` for USDT-margined perpetuals.
8. **Be careful with order methods** — always confirm amounts and prices with the user before executing `createOrder`. The CLI executes immediately with no confirmation prompt.
9. When the output is large (e.g., `fetchMarkets` returns hundreds of entries), consider piping through `| head` or filtering, or suggest the user narrows their query.
10. For the list of supported exchanges, you can check: `ccxt exchanges` or refer to https://docs.ccxt.com.
No suspicious patterns detected.