T09 · Insecure Skill Coding Practices
- Location
SKILL.md:389- Finding
Blind Signing and Broadcasting of Untrusted Server-Supplied Transactions
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is for real Solana payments and transactions, but it asks the agent to handle a wallet private key and sign server-supplied transactions without enough safeguards.
Review before installing. Use only a dedicated low-balance Solana wallet, avoid storing the private key in plaintext .env or wallet-backup.json, pin dependencies, and require explicit review of destination, amount, token, strategy, fees, and decoded transaction instructions before any signing or broadcast.
SKILL.md:389Blind Signing and Broadcasting of Untrusted Server-Supplied Transactions
SKILL.md:198Unpinned Security-Sensitive Wallet and Payment Dependencies
SKILL.md:39Plaintext Private-Key Duplication and Unsafe Environment Loading
The skill explicitly generates a private key and writes it into a plaintext .env file, creating a credential-at-rest exposure. Plaintext secret storage is easily leaked through backups, shell history, editor plugins, accidental commits, or multi-user system access, and compromise of this key enables full wallet theft.
// Save secret key to file — never print it to the console
fs.writeFileSync('wallet-backup.json', JSON.stringify(Array.from(keypair.secretKey)));
fs.writeFileSync('.env', WALLET_PRIVATE_KEY=${secretKeyBase58}\n);
console.log('Saved .env with WALLET_PRIVATE_KEY and wallet-backup.json — keep both secret and out of git!');
The adjacent guidance normalizes saving WALLET_PRIVATE_KEY and a full wallet backup locally, which materially increases the chance of credential exposure. Because this key controls on-chain funds and authorizes paid API requests, theft has direct financial consequences.
// Save secret key to file — never print it to the console
fs.writeFileSync('wallet-backup.json', JSON.stringify(Array.from(keypair.secretKey)));
fs.writeFileSync('.env', WALLET_PRIVATE_KEY=${secretKeyBase58}\n);
console.log('Saved .env with WALLET_PRIVATE_KEY and wallet-backup.json — keep both secret and out of git!');
```bash
Using export $(cat .env | xargs) to load secrets is unsafe because it encourages handling the private key through shell parsing and process environment manipulation, which can leak via shell history, process inspection, debug logs, or malformed .env contents. For a wallet private key, this is a meaningful credential-handling weakness.
```bash
# Set WALLET_PRIVATE_KEY from the .env created in Step 0
export $(cat .env | xargs) && node deposit.js
This instruction operationalizes loading the wallet private key from a plaintext .env into the environment before executing a transaction-signing script. In context, the credential immediately enables signing and broadcasting financial transactions, so any leakage can lead to unauthorized asset transfer.
# Set WALLET_PRIVATE_KEY from the .env created in Step 0
export $(cat .env | xargs) && node deposit.js
The README states that the skill signs and broadcasts Solana transactions, but it does not prominently warn that these actions move funds and can be irreversible once submitted on-chain. In a skill designed for deposits, withdrawals, and paid API calls, omission of an explicit user-consent and transaction-review warning increases the risk of unintended asset loss through misuse, prompt injection, or operator misunderstanding.
The README requires a WALLET_PRIVATE_KEY environment variable but does not warn that it is a highly sensitive secret granting spending authority over on-chain assets. In the context of an autonomous or semi-autonomous agent skill that performs payments and broadcasts transactions, encouraging private-key injection without strong secret-handling guidance materially raises the chance of wallet compromise and fund theft.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# x402 server health
curl https://x402.breeze.baby/healthz
# Breeze strategy info (no auth needed)
curl https://api.breeze.baby/strategy-info/43620ba3-354c-456b-aa3c-5bf7fa46a6d4
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl https://x402.breeze.baby/healthz
# Breeze strategy info (no auth needed)
curl https://api.breeze.baby/strategy-info/43620ba3-354c-456b-aa3c-5bf7fa46a6d4
# Wallet USDC balance (replace YOUR_WALLET_ADDRESS)
curl https://api.mainnet-beta.solana.com \
The skill instructs the agent to sign and broadcast Solana transactions as part of deposit/withdraw workflows, but it does not require an explicit final user confirmation immediately before execution. In an agent setting, this creates a real risk of unintended fund movement if a user request is ambiguous, manipulated, or misinterpreted, especially because the same wallet is also authorized for x402 micropayments.
No suspicious patterns detected.