Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Bounty Hunter Skill
v1.0.5Operate the Niuma Bounty task platform on XLayer testnet: query, post, join, submit, review tasks, bidding, balance check, and build unsigned transactions.
⭐ 0· 88·1 current·1 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 name/description (operate/query/post/join/submit/review/build unsigned txs) mostly matches the code's read/query and unsigned-tx-building capabilities. However SKILL.md and README repeatedly advertise direct write commands (create, join, submit, approve, etc.) that imply signing and broadcasting transactions; those direct write commands are not implemented in scripts/niuma.js. This mismatch between advertised write capabilities and the actual code is a substantive incoherence.
Instruction Scope
SKILL.md instructs users to set NIUMA_WALLET_SECRET for write operations and shows many write CLI commands. The actual runtime script implements read-only queries and a build-tx command that returns unsignedTxs for external signing; the script never reads or uses NIUMA_WALLET_SECRET. The instructions therefore overstate the skill's runtime behavior and could mislead users into exposing private keys unnecessarily.
Install Mechanism
There is no special installer (npm install is the expected step). However package-lock.json contains resolved URLs pointing to http://mirrors.tencentyun.com (plain HTTP). A lockfile that references HTTP mirrors may cause npm to fetch packages over insecure channels depending on registry configuration — this raises supply-chain risk and should be reviewed before running npm install.
Credentials
Registry metadata lists no required env vars or primary credential, but SKILL.md claims write operations require NIUMA_WALLET_SECRET and also documents NIUMA_RPC as override. The shipped code only uses NIUMA_RPC (and not NIUMA_WALLET_SECRET). The mismatch is a red flag: instructions ask for a private key that the code does not need, which could trick users into exposing secrets for no reason.
Persistence & Privilege
The skill does not request always:true, does not ask for system-wide config paths, and is user-invocable only. It does not persist or modify other skills' configuration. No elevated persistence privileges detected.
What to consider before installing
Do not supply your private key (NIUMA_WALLET_SECRET) to this skill because the code does not use it — the script only queries the chain and builds unsigned transactions for external signing. Before installing/running: (1) prefer using build-tx + a trusted wallet plugin to sign and broadcast transactions rather than giving a key to the skill; (2) inspect or re-generate package-lock.json to ensure packages are fetched from trusted HTTPS registries (the lockfile references http://mirrors.tencentyun.com); (3) run npm install in an isolated environment (container/VM) and review node_modules if you must install; (4) consider contacting the publisher or using a fork that removes misleading instructions; and (5) if you need direct write capabilities, only use a version where the code explicitly implements signing and clearly documents why it needs private keys.Like a lobster shell, security has layers — review code before you run it.
latestvk97czapb0jbrb6bjt3bda4xn2183gcmg
License
MIT-0
Free to use, modify, and redistribute. No attribution required.