Back to skill
Skillv1.0.0
ClawScan security
Contract Scanner · ClawHub's context-aware review of the artifact, metadata, and declared behavior.
Scanner verdict
SuspiciousMar 6, 2026, 5:54 AM
- Verdict
- suspicious
- Confidence
- high
- Model
- gpt-5-mini
- Summary
- The skill claims to scan contracts using external services but its code and instructions do not actually use the declared API key or tools and overpromise features — this mismatch is suspicious and should be clarified before use.
- Guidance
- This package appears to be a stub or an overpromising toy rather than a working contract scanner. Before installing or providing any API keys: 1) Ask the author for the source/origin and why ETHERSCAN_API_KEY and curl are required. 2) Request a version that actually calls the declared APIs (examples of network calls that use your key) or remove the requirement. 3) Only supply an API key in a sandboxed environment or use a limited/test key until you verify behavior. 4) If you need real scanning, prefer tools with verifiable provenance and documented integrations (e.g., public GitHub repo, known scanners). 5) If you plan to run the included script, inspect it locally first — it currently only prints simulated results and does not exfiltrate data, but the mismatch between claims and code is a risk sign.
Review Dimensions
- Purpose & Capability
- concernThe skill's stated purpose is contract scanning using services like Etherscan/TokenSniffer, but the shipped implementation (scanner.py) only prints simulated, hard-coded results and does not call any blockchain APIs or analyzers. The registry metadata requires ETHERSCAN_API_KEY and lists curl, but neither is used by the provided code. The SKILL.md also advertises features (real-time alerts, API access, deep analysis) that are not implemented in the code bundle.
- Instruction Scope
- noteSKILL.md gives usage/command examples and declares required env/binaries, but the runtime instructions do not describe any network/API usage or data flows. The instructions are high-level and do not show how an ETHERSCAN_API_KEY would be used, nor do they instruct reading user files or other sensitive data. However, the combination of vague instructions and a non-functional scanner implementation is a red flag.
- Install Mechanism
- okThere is no install spec (instruction-only pattern) and no external archives are downloaded. Only a single Python file is included. This is the lower-risk install pattern, but note the file content does not match the claimed behavior.
- Credentials
- concernThe skill requires ETHERSCAN_API_KEY (a sensitive credential) and lists curl in required binaries, yet the included Python script does not read environment variables, invoke curl, or perform network queries. Requesting a sensitive API key without using it is disproportionate and suspicious because it offers no clear justification for needing that secret.
- Persistence & Privilege
- okThe skill is not always-enabled, does not request persistent system-wide changes, and contains no install-time behavior that would grant it ongoing privileges. There is no evidence it modifies other skills or system config.