T09 · Insecure Skill Coding Practices
- Location
SKILL.md:32- Finding
Authentication Secret Exposed in a State-Changing GET Request
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a coherent trading skill, but it documents high-impact financial actions and sensitive key handling in ways users should review carefully before installing.
Install only if you understand that this skill can guide Decker/Hyperliquid trading actions and may involve giving Decker a trade-capable private key. Use a dedicated low-risk API wallet, confirm every order manually, avoid putting secrets in URLs or logs, and check whether Decker provides key storage, revocation, replay protection, and order limits.
SKILL.md:32Authentication Secret Exposed in a State-Changing GET Request
SKILL.md:45External Service Receives a Transaction-Signing Private Key
The documentation shows a GET request that places a secret value (openclaw_secret) directly in the URL query string. Secrets in URLs are commonly exposed through logs, browser history, intermediary proxies, monitoring tools, and referrer leakage, making credential compromise more likely; in this context, compromise could enable unauthorized order-request generation against a trading workflow.
The trigger list includes broad terms such as "DEX," "영구선물," and generic price/position phrases that can match ordinary crypto discussion, causing the trading skill to activate outside clear user intent. In a skill capable of facilitating order flows, over-broad invocation increases the chance of inappropriate tool routing and accidental progression toward sensitive trading actions.
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
## 참고
- 메인 decker 스킬: `docs/openclaw_skills/decker/SKILL.md`
- Hyperliquid: 탈중앙 영구선물 DEX