T09 · Insecure Skill Coding Practices
- Location
index.js:31- Finding
Unvalidated CLI Input Allows API Route and Query Manipulation
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill appears purpose-built for DeFi analysis, but its automatic paid API calls have inconsistent price disclosures and weak runtime controls.
Review this skill before installing. It sends wallet or position identifiers to a remote DeFi API and may cause automatic USDC x402 charges on Base. Only use it in an environment where you can confirm or cap spending, and treat the published per-action prices as ambiguous until the publisher makes them consistent.
index.js:31Unvalidated CLI Input Allows API Route and Query Manipulation
SKILL.md:41Conflicting Price Disclosures Can Cause Unexpected Cryptocurrency Charges
The skill declares environmental requirements and network/payment capabilities but does not define an explicit tool scope such as permissions or allowed-tools. That ambiguity can let an agent invoke the skill with broader-than-expected access, making unintended data exposure or external calls more likely.
The skill describes wallet position scanning and optimization but does not prominently warn that wallet addresses and DeFi position data are sent to external services. Even though blockchain data is public, linking a user's queried wallets, positions, and behavior to a third-party API creates privacy and profiling risks.
The trigger phrases are broad and could cause the skill to activate on generic DeFi-related requests without clear user intent boundaries. In this skill, that is more dangerous because activation may result in paid external API calls and transmission of wallet-related data to a third party.
The skill advertises automatic x402 micropayments per call without a prominent user warning or consent flow at the point of use. Combined with broad triggers, this can lead to unintended charges from ordinary requests, making the risk more severe than a typical disclosure issue.
The CLI sends user-supplied wallet addresses or position identifiers to a remote API endpoint without any just-in-time disclosure, confirmation, or privacy warning at execution time. In a DeFi context, these identifiers can reveal portfolio composition, LP activity, and financial behavior, creating privacy and profiling risk even if the data is public on-chain.