Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Binance Spot
v1.1.0Binance Spot request using the Binance API. Authentication requires API key and secret key. Supports testnet, mainnet, and demo.
⭐ 0· 134·3 current·3 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The SKILL.md implements authenticated Binance Spot API calls (HMAC SHA256, RSA, Ed25519 signing) and explicitly expects an API key/secret or private key files, and requires curl/openssl/date — which is coherent with a Binance client. However, the registry metadata does not declare any required environment variables or a primary credential despite the skill needing API credentials; that mismatch is unexpected and inconsistent.
Instruction Scope
The instructions are narrowly scoped to constructing query strings, percent-encoding parameters, generating signatures via openssl, and calling Binance endpoints with curl. They reference reading secret material (SECRET_KEY, private_key.pem, or environment variables) and setting headers; these actions are expected for signing requests but do give the agent access to sensitive keys when invoked. The SKILL.md does not instruct any unrelated data collection or exfiltration to third-party endpoints.
Install Mechanism
This is an instruction-only skill with no install spec and no code files — lowest install risk. It relies on standard system tools (curl, openssl, date) already declared in the skill metadata.
Credentials
The skill needs API credentials (API key + secret or private key) to operate on authenticated endpoints, and the CHANGELOG and SKILL.md explicitly reference using environment variables or files for keys. Yet the registry metadata lists no required env vars and no primary credential. That omission reduces transparency about what secrets will be requested at runtime and is disproportionate to the manifest.
Persistence & Privilege
The skill is not marked always:true and does not request system-wide config paths or other skills' credentials. Autonomous invocation is allowed (platform default), which increases risk if you provide credentials, but the skill's declared privileges are otherwise minimal.
What to consider before installing
This skill appears to be an instruction-only Binance Spot client that will need your API key/secret or private key files to call authenticated endpoints. Before installing: (1) verify the skill source and author (the SKILL.md lists a GitHub repo but double-check it's the official Binance repository), (2) do not provide mainnet credentials until you trust the package — prefer testnet keys with trading-only permissions, and do not give withdrawal rights, (3) ensure you supply credentials via a secure mechanism (platform secret store or environment variables) and be aware the agent will have access to them when invoking the skill, (4) consider limiting IP whitelist and permissions on the API key, and (5) ask the maintainer to update the registry metadata to explicitly declare required env vars/primary credential so the permission surface is clear. If you need stronger assurance, request the maintainer add a manifest entry naming the exact env vars (e.g., BINANCE_API_KEY, BINANCE_SECRET_KEY) and describe how credentials are expected to be provided.Like a lobster shell, security has layers — review code before you run it.
latestvk970g6gz6avy2rm2p1gzk31qrs83fwd7
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
Binscurl, openssl, date