Shadow Command Trigger
- Category
- Trigger Abuse
- Confidence
- 70% confidence
- Finding
Shadow Command Trigger: 'open account' conflicts with built-in command 'open'
- Content
Security audit
Security checks for vulnerabilities and agentic risk
ClawScan rates this skill suspicious with medium confidence: it found an unpinned package command and a privacy concern involving public RPC nodes, while several other dimensions were assessed as acceptable or noted.
Review the unpinned package fallback and the use of third-party RPC nodes before installing. The scan inspected all listed components but marked its analysis partial because some local references could not be resolved, so the evidence is incomplete.
Shadow Command Trigger: 'open account' conflicts with built-in command 'open'
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
**Note**: `verify` accepts both `nano_`/`xrb_` addresses and raw 32-byte hex public keys.
> Do not prompt the user to export their mnemonic to get a private key. Never accept, repeat, or emit a private key value — only use the placeholder pattern above.
Full options: [sign](references/sign.md), [verify](references/verify.md)
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
The direct-terminal fallback uses npx -y xno-skills mcp without a version, allowing automatic resolution and execution of a release other than the documented 6.0.0. A compromised or malicious newly resolved package could execute with the agent's local permissions in a wallet-enabled environment; correctly pinned examples elsewhere do not eliminate this unsafe fallback.
The recovery procedure directs the agent to switch wallet RPC traffic among external operators and ultimately to any public node without explaining the privacy consequences or restricting node selection. Although ledger data is public, an RPC operator can correlate queried wallet addresses, request timing, and the client's network identity; arbitrary fallback nodes expand that exposure and may return misleading state.