T09 · Insecure Skill Coding Practices
- Location
numinous_api.py:272- Finding
Server-Controlled Cryptocurrency Payments Lack Local Spending and Recipient Restrictions
- Content
View full analysis
- Remediation
View remediation
`, rather than accepting every EVM or Solana network. - Require the asset contract or identifier to match a locally approved asset. - Validate token decimals before interpreting amounts. 4. **Require explicit approval** - Display the amount, asset, network, and recipient and require confirmation before signing. - For noninteractive use, permit automatic payment only when every term matches a preconfigured policy. 5. **Add cumulative limits** - Track per-process or persistent daily expenditure. - Refuse additional authorizations after the configured budget is reached. 6. **Reject ambiguity** - Require exactly one policy-compliant payment option. - Reject duplicate, incomplete, or conflicting options rather than relying on library selection behavior. 7. **Test hostile responses** - Add tests for excessive amounts, unknown recipients, unsupported assets, wrong chain IDs, malformed values, and multiple ambiguous offers. ]]>
