Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Binance Event Contract Risk Manager
v1.0.0Continuously manages Binance BTCUSDT and ETHUSDT event contract risks by enforcing position sizing, daily loss limits, exposure caps, and emergency circuit b...
⭐ 0· 148·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
high confidencePurpose & Capability
The skill's stated purpose (monitoring balances, open positions, cumulative P&L, enforcing trade limits on BTCUSDT/ETHUSDT) inherently requires access to Binance account data and/or market data (API keys, account id, endpoints). However the skill declares no required environment variables or credentials. That omission is inconsistent: a risk manager operating on live accounts would legitimately need API credentials and access details.
Instruction Scope
SKILL.md gives concrete rules, triggers, and checks (daily P&L, exposure across open positions, contract expiry warnings) but contains no concrete instructions for obtaining account state, market data, or where signals come from. It assumes continuous access to account and API responses without specifying endpoints, auth, or data sources — leaving the agent broad discretion and ambiguity about how data will be accessed or stored.
Install Mechanism
This is an instruction-only skill with no install spec or code files. The only install hint is a user-level 'npx clawhub install ...' example in SKILL.md, which is benign documentation. No archives, downloads, or package installs are declared, so there is no installation-time code risk from the skill itself.
Credentials
No environment variables or primary credential are declared despite the skill needing Binance API access in practice. This is disproportionate: the skill should declare the exact credentials it requires (e.g., BINANCE_API_KEY, BINANCE_API_SECRET) and justify scopes (read-only vs trading). The omission raises the risk that an agent might attempt to use other available credentials implicitly or requires ad-hoc sharing of secrets.
Persistence & Privilege
The skill is not always-enabled, is user-invocable, and does not declare any persistent system changes. It does allow autonomous invocation (platform default) but that alone is not unusual or flagged here.
What to consider before installing
Do not install or enable this skill for real trading until these inconsistencies are resolved. Specifically: (1) confirm the skill's source and review its code — there are no code files provided here; (2) require the skill to explicitly declare which environment variables/credentials it needs (e.g., BINANCE_API_KEY, BINANCE_API_SECRET, ACCOUNT_ID) and which API scopes are required (read-only vs trade/cancel); (3) insist on a clear, auditable integration path for account data (which endpoints, how P&L is computed, where logs are stored); (4) test in a sandbox/paper-trading environment first and only provide minimal permissions (prefer read-only) until you trust behavior; and (5) if you cannot review the implementation, avoid giving this skill any live trading credentials because the current SKILL.md implies access to sensitive account operations but does not document or declare them.Like a lobster shell, security has layers — review code before you run it.
latestvk97bwvmfyt9vvg263t7v91n32d8343q3
License
MIT-0
Free to use, modify, and redistribute. No attribution required.