usd1 transfer
WarnAudited by ClawScan on May 10, 2026.
Overview
Review before use: this skill performs a wallet transfer using a raw private key and does not show strong confirmation or scoping safeguards, though it appears limited to Testnet and shows no exfiltration.
Install only if you are comfortable giving the agent a disposable testnet wallet private key and authorizing a token transfer. Do not use a real or reused wallet key, and verify the recipient, amount, chain, and actual Wormhole transfer mechanism before running it.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If you provide a reused or real wallet private key, the skill or agent session could authorize wallet transactions with that key.
The skill asks the agent for a raw wallet private key, which is full signing authority for that wallet. This is sensitive authority and is not reflected as a declared primary credential in the registry metadata.
- privateKey: string (secure, required) - sender wallet private key
Use only a disposable testnet-only wallet key, never a mainnet or reused private key. Prefer a wallet/signer flow that prompts for each transaction and declare the credential requirement clearly.
A wrong recipient, wrong amount, or unintended autonomous invocation could move tokens using the provided wallet key. Testnet reduces real-fund impact, but the key handling remains sensitive.
The handler directly executes a blockchain token transfer using caller-supplied amount, recipient, chain, and private key. The artifacts do not show a final user-confirmation gate, address validation policy, amount cap, or recipient allowlist.
const transfer = await wh.tokenBridge().transfer(
privateKey,
chain,
transferAmount,
'USDC',
new UniversalAddress(toAddress, 'hex')
);Require explicit user confirmation immediately before signing, validate chain and address formats, enforce Testnet-only operation, and consider configurable transfer limits.
Dependency crypto issues could increase risk if the SDK path uses the affected code with private keys.
A transitive dependency in the locked npm tree carries a crypto-related deprecation warning. It appears to come from expected Wormhole SDK dependencies, but it is relevant because this skill handles private keys.
"@cosmjs/crypto": { ... "deprecated": "This uses elliptic for cryptographic operations, which contains several security-relevant bugs... private keys might still be at risk."Review the dependency tree, update to versions that avoid deprecated crypto packages where possible, and avoid providing valuable private keys to this skill.