Skillv1.1.1

ClawScan security

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

Scanner verdict

SuspiciousFeb 11, 2026, 9:43 AM

Verdict: suspicious
Confidence: high
Model: gpt-5-mini
Summary: The skill's code and instructions match its stated purpose (playing an on‑chain Blinko game), but it requires a highly sensitive WALLET_PRIVATE_KEY (not declared in the registry metadata) and will sign and submit real ETH transactions to hardcoded external endpoints — proceed only after understanding the financial risk and source provenance.
Guidance: This skill appears to do exactly what it says (play Blinko on Abstract) and contains the code to sign and submit real ETH transactions. Key points before installing: (1) The skill requires your private key (WALLET_PRIVATE_KEY) — this gives full control of that wallet. Use a dedicated hot wallet with only the funds you are willing to lose. (2) Registry metadata omitted the env var; ask the publisher why that mismatch exists and confirm the skill's provenance. (3) The skill talks to hardcoded endpoints (https://api.blinko.gg and https://api.abs.xyz) and a hardcoded contract address — verify those addresses are legitimate before use. (4) If you install, prefer manual invocation (disable autonomous agent actions or require confirmation) and inspect/run the code in an isolated environment. (5) If you only want read‑only info, consider using stats.js with a watch‑only address instead of providing a private key. If you need higher assurance, ask the publisher for a signed source/release or run the scripts on a throwaway wallet with minimal funds first.

Review Dimensions

Purpose & Capability: noteThe name/description and included scripts (play-blinko.js, stats.js) are coherent: the skill logs in, requests a server seed, calls createGame/cashOut on the on‑chain contract, and queries stats from api.blinko.gg. However the registry metadata at the top claimed no required env vars, while SKILL.md and the scripts clearly require WALLET_PRIVATE_KEY. That metadata mismatch is an inconsistency the publisher should explain.
Instruction Scope: okSKILL.md and the scripts are specific about actions: sign a login message, obtain a JWT, call the Blinko API, call Abstract RPC to create and settle on‑chain games, and show stats. The instructions do not attempt to read unrelated files or hidden credentials. They do transmit signatures and JWTs to api.blinko.gg and send signed transactions to the RPC endpoint (expected for this purpose).
Install Mechanism: okThere is no installer that downloads arbitrary archives; this is instruction + source files with a simple package.json (ethers dependency). Risk is limited to running npm install / node on the files you download; no obscure remote installers or shortener URLs are used.
Credentials: concernThe skill requires a single, highly sensitive environment variable: WALLET_PRIVATE_KEY (declared in SKILL.md metadata). That is proportionate to playing an on‑chain game, but it grants full control of the wallet's funds. The earlier registry section incorrectly listed no required env vars — this mismatch is concerning. No other credentials are requested, which is expected, but the private key risk is material.
Persistence & Privilege: notealways:false (good). The skill indicates agents may invoke it autonomously (default platform behavior). Because the skill can sign and submit transactions that spend ETH, autonomous invocation increases risk — consider restricting autonomous use or requiring user confirmation before any transaction is sent.