ClawHub
Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

one-wallet

v1.0.0

Helps the agent use the one-wallet CLI to manage Ethereum/EVM wallets, send transactions, call contracts, and sign data. Use when the user mentions one-walle...

⭐ 0· 98·0 current·0 all-time
byJerry@viyozc
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The name and description match the SKILL.md content: the file is a focused how-to for the one-wallet CLI (wallet management, sending txs, signing). It requires no unusual binaries, env vars, or config paths beyond the expected assumption that one-wallet (or Node.js for building) is available. The absence of required env vars or install specs is consistent with an instruction-only skill.
ℹ
Instruction Scope
Instructions stay within the wallet/CLI domain (creating/importing wallets, sending transactions, signing). However, many examples show workflows that require sensitive secrets (private keys, mnemonics, or RPC provider API keys) and commands that expose wallet storage locations (one-wallet wallet path). The instructions do not direct the agent to read unrelated system files or exfiltrate data, but they do encourage actions that, if performed carelessly, could expose secrets (e.g., inline private keys or plaintext provider URLs).
ℹ
Install Mechanism
There is no platform install spec (lowest-risk). The SKILL.md includes normal install guidance (npm/yarn/pnpm global install) and an optional git clone of a GitHub repo. That is proportionate, but users should verify the npm package and the GitHub repo before installing or running ./bin/run.js from a cloned repo.
ℹ
Credentials
The skill declares no required environment variables or credentials, which is reasonable for an instruction-only helper. Practically, many operations described require user-supplied secrets (private keys, mnemonics, or RPC API keys). The SKILL.md does not request unrelated credentials; the sensitive items are appropriate to the wallet management purpose but need careful handling by the user.
✓
Persistence & Privilege
The skill is not always-enabled and is user-invocable; it does not request persistent system privileges or modify other skills' configuration. No elevated persistence or automatic installation is present.
Assessment
This skill is a straightforward CLI recipe for the one-wallet tool and appears internally consistent, but it involves handling sensitive secrets. Before using: (1) Verify the one-wallet binary/package and repository (confirm the npm package owner and GitHub repo contents) rather than blindly running git clone or npm install. (2) Never paste private keys, mnemonics, or API keys into chat; prefer using secure local storage, hardware wallets, or environment variables protected from logs. (3) Avoid running ./bin/run.js from an unreviewed clone. (4) When scripting, avoid embedding secrets on the command line (use protected env vars or prompting). (5) If you only need read-only queries, run operations that do not require wallet keys. If you want further help, provide the exact risk model (local machine vs. CI vs. remote host) and I can give concrete safe usage patterns.

Like a lobster shell, security has layers — review code before you run it.

latestvk972vv818aq1wf8kaxw1x7s949833ea6

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments