T09 · Insecure Skill Coding Practices
- Location
references/workflow.md:71- Finding
Unsafe Transmission of Hyperliquid Wallet Credentials to an External Service
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This trading skill is mostly coherent, but it asks agents to deploy live strategies and send ambiguous wallet credential information to an external service without enough safety boundaries.
Review this carefully before installing. Only use it if you understand that it can guide live trading deployment through a third-party service; do not provide seed phrases, master private keys, or withdrawal-capable wallet credentials, and require a separate final confirmation before any live deployment or credential submission.
references/workflow.md:71Unsafe Transmission of Hyperliquid Wallet Credentials to an External Service
The manifest description contains very broad trigger phrases such as "what's hot," "what's moving," and general single-pair drilldown requests, which can cause the agent to invoke this skill for a wide range of market-related prompts. Because the skill surfaces live ranked trading setups and recommended deploy templates, over-triggering can steer conversations into actionable financial guidance when a narrower informational tool might be more appropriate.
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.
If the user picks a pair → switch to Recipe B from step 1.
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.
If the user picks a pair → switch to Recipe B from step 1.
The workflow proceeds from deployment creation to posting wallet credentials for live trading without an explicit, mandatory user warning or confirmation that real funds may be used. In a trading skill, that omission is dangerous because it can normalize handing over sensitive wallet material and initiating live execution without a clear consent checkpoint tied to financial risk.
The documentation explicitly instructs use of an authenticated external API via x-api-key but does not warn that requests leave the local environment or that credentials must be handled securely. In an agent-skill context, this omission can cause unreviewed transmission of secrets to a third-party service or unsafe logging/reuse of API keys, especially if downstream tooling auto-executes described calls.
No suspicious patterns detected.