Skillv1.0.0

ClawScan security

Broadcast Signed Transaction · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

BenignFeb 27, 2026, 8:50 AM

Verdict: benign
Confidence: high
Model: gpt-5-mini
Summary: The skill is internally coherent for broadcasting pre-signed transactions via the OKX Web3 API and the included script implements that behavior, but the package metadata fails to declare the required OKX environment variables — review before use.
Guidance: This skill implements exactly what it claims: it POSTS a provided signed transaction hex to the OKX Web3 broadcast endpoint and returns orderId/txHash. Before installing or using it: 1) Note the registry metadata omits required env vars — you must supply OKX_ACCESS_KEY, OKX_SECRET_KEY and OKX_PASSPHRASE (use OKX Web3 API Key as the SKILL.md instructs). 2) Do not provide your private wallet key to this skill — the script doesn't need it. 3) Only use OKX credentials with the minimum necessary permissions and consider using a throwaway/test key first (or testnet) to confirm behavior. 4) Review the full script locally to confirm no unexpected network endpoints (the code posts only to https://web3.okx.com). 5) Because the skill can broadcast transactions, treat its API keys as sensitive: run in an environment you control, and rotate keys if you suspect misuse. 6) Ask the publisher to correct the metadata to declare the required environment variables and provide a homepage/source attribution for better trust.

Review Dimensions

Purpose & Capability: concernThe skill's name, description, SKILL.md and the included Python script all consistently implement broadcasting already-signed transaction hexes to chain(s) via the OKX Web3 Broadcast API — this is coherent. However, the registry metadata lists no required environment variables or credentials while the SKILL.md and the script clearly require OKX_ACCESS_KEY, OKX_SECRET_KEY and OKX_PASSPHRASE. That mismatch reduces transparency and is an incoherence that should be corrected.
Instruction Scope: noteRuntime instructions describe collecting chainIndex, address, signedTx and optional --mev, validating parameters, and calling the included script which only reads the declared OKX env vars and performs an HTTP POST to OKX. This stays within the stated purpose. Minor note: SKILL.md text mentions extracting chain/address from 'logs/context' which is vague and could encourage broader context access; the code itself does not perform arbitrary system/file reads.
Install Mechanism: okNo install spec (instruction-only plus an included Python script). Dependency is only 'requests' (documented). No downloads or arbitrary remote installs, no archive extraction — low install risk.
Credentials: noteThe script requires OKX Web3 API credentials (OKX_ACCESS_KEY, OKX_SECRET_KEY, OKX_PASSPHRASE) which are appropriate and necessary for calling OKX's broadcast API. This is proportionate to the skill's purpose. However, those env vars are not declared in the registry metadata (declared 'none'), which is a transparency issue. The skill explicitly states it does not need WALLET_PRIVATE_KEY (good).
Persistence & Privilege: okThe skill does not request persistent installation privileges (always: false), does not modify other skills or system settings, and does not store credentials itself. Autonomous invocation is allowed (platform default) but not combined with other concerning privileges.