Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Binance P2p
v1.0.0Binance P2P trading assistant. Use when asked about P2P prices, ads, payment methods, or P2P order history. NOT for spot/futures prices or exchange trading.
⭐ 0· 36·0 current·0 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 clearly supports both public (no-auth) queries and authenticated personal-order endpoints that require BINANCE_API_KEY and BINANCE_SECRET_KEY. However, the registry metadata lists no required environment variables or primary credential. This is an internal inconsistency: a Binance P2P order-history feature legitimately needs API credentials, so the registry should declare them. The lack of a homepage/owner context increases uncertainty.
Instruction Scope
The instructions themselves are focused on P2P queries and SAPI-authenticated order history and provide detailed signing guidance (HMAC SHA256, percent-encoding, SAPI parameter ordering). They instruct the agent to use env vars for credentials, to mask secrets in outputs, and to prefer not writing secrets to disk unless the user consents. They also include concrete shell examples (openssl, curl) which are expected for HMAC signing but give the agent explicit shell-level operations — normal for this task but worth noting. The unusual SAPI requirement to preserve insertion order for parameters is highlighted; while this may be valid for Binance P2P SAPI, it is nonstandard and should be validated against official docs.
Install Mechanism
This is an instruction-only skill with no install spec and no code files. Nothing is written to disk or downloaded by default, which minimizes installer risk.
Credentials
The SKILL.md requires two sensitive environment variables (BINANCE_API_KEY and BINANCE_SECRET_KEY) for personal-order features, which is proportionate to the claimed Phase 2 capability. However, the registry metadata declares no required env vars or primary credential — an inconsistency that could hide the fact the skill needs secrets. Requesting both API key and secret is expected for signed requests, but the skill should declare these formally and document required minimum permissions (it does recommend read-only).
Persistence & Privilege
The skill is not always-on and does not request system-wide config paths or other skills' configs. The SKILL.md explicitly discourages writing secrets to disk without explicit user consent and suggests .env with .gitignore. Autonomous invocation is allowed by platform default, but the skill does not request elevated persistence privileges.
What to consider before installing
This skill appears to implement what it claims (Binance P2P public queries plus optional authenticated order-history), but there is a clear mismatch: the bundled SKILL.md expects BINANCE_API_KEY and BINANCE_SECRET_KEY while the registry metadata lists no credentials. Before installing or providing secrets:
- Ask the publisher/owner to correct the registry metadata so required env vars and primary credential are explicit. A trustworthy skill should declare its need for secrets in the registry.
- If you must enable personal-order features, create a dedicated Binance API key with the minimum permissions (reading only), enable IP whitelist, and avoid using a key tied to large balances.
- Prefer injecting keys at runtime/session (not writing to disk). If you must store them, only save to disk with your explicit consent and ensure the file is in .gitignore and protected.
- Verify the SAPI signing instructions against Binance's official docs (the 'do not sort parameters' claim is unusual and should be confirmed).
- Because the skill is instruction-only, it will run curl/openssl-style commands to sign and call endpoints; restrict execution environment and do not supply secrets to untrusted agents.
If you cannot confirm the publisher or do not want to share secrets, use only the public (no-auth) features or consider declining installation.Like a lobster shell, security has layers — review code before you run it.
latestvk974xd7ygmhzdxmyff19e5d9fd841dw1
License
MIT-0
Free to use, modify, and redistribute. No attribution required.