Binance Pro 1.0.0
AdvisoryAudited by Static analysis on Apr 30, 2026.
Overview
No suspicious patterns detected.
Findings (0)
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 used with trading-enabled keys, the agent could place or cancel orders, change leverage, or open leveraged positions, potentially causing financial loss.
The skill documents raw Binance API calls that can place futures orders and broadly advertises 'any Binance operation.' These are high-impact financial actions, and the artifact does not require explicit per-trade approval, size/leverage limits, or testnet-only operation.
description: Complete Binance integration ... Trade spot, futures with up to 125x leverage ... and any Binance operation. ... curl -s -X POST "https://fapi.binance.com/fapi/v1/order?..."
Require explicit user confirmation for every account-mutating action, including symbol, side, quantity, order type, price, and leverage. Prefer testnet or read-only keys unless active trading is truly intended.
A trading-enabled Binance key could allow the agent to act on the user's exchange account, not just view data.
The skill asks for Binance API credentials that can authenticate account actions. Combined with the documented trading calls, these credentials may grant broad financial authority, while the registry requirements declare no primary credential or required environment variables.
Save to `~/.openclaw/credentials/binance.json`: { "apiKey": "YOUR_API_KEY", "secretKey": "YOUR_SECRET_KEY" } ... export BINANCE_API_KEY="your_api_key" ... export BINANCE_SECRET="your_secret_key"Use least-privilege Binance API keys: disable withdrawals, restrict IPs if possible, grant read-only access unless trading is necessary, and create separate low-limit keys for automation.
Users may have less assurance that the reviewed package identity matches the registry listing they expect.
The packaged metadata does not exactly match the registry metadata shown for this review, which lists a different owner ID and slug. This is not evidence of malicious behavior, but it is a provenance ambiguity for a high-impact financial skill.
"ownerId": "kn71h1rbedy5za6d4cadf230zn80d89f", "slug": "binance-pro"
Verify the publisher, registry listing, and version before granting Binance credentials or using the trading instructions.