T09 · Insecure Skill Coding Practices
- Location
SKILL.md:16- Finding
Hardcoded Shared API Credential Exposed in Documentation
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is mostly coherent for OKX blockchain data workflows, but it publishes and encourages installing a shared API key in a wallet and swap-related context.
Review this skill before installing. Its OKX MCP workflow is disclosed and includes confirmation for swap-related operations, but do not use the embedded shared demo key for regular work. Use your own least-privilege OKX key through an environment variable or secret manager, avoid pasting secrets into shell commands, and require explicit confirmation before any approve, swap, or transaction-instruction operation.
SKILL.md:16Hardcoded Shared API Credential Exposed in Documentation
The declared description says the skill is for using OKX OnchainOS MCP through UXC to perform blockchain-related data access and swap-planning tasks. However, the supplied code chunk only validates that the skill's markdown and YAML files contain required documentation, example commands, endpoint references, and metadata. Its primary purpose is CI/documentation linting for the skill package, not operating the OKX MCP tooling itself. This is a material description-behavior mismatch, not merely an implementation detail.
The documentation contains a hard-coded API credential and instructs users to install it for "quick trial auth," which is an unsafe secret-distribution pattern. Even if intended as a demo key, publishing shared credentials enables unauthorized reuse, abuse of the upstream service, and accidental propagation of a secret into shells, histories, logs, screenshots, and downstream automation.
The file not only exposes a shared API credential but actively encourages its use without any safety warning, normalizing insecure credential-sharing practices. In a skill that supports wallet, balance, and swap-related workflows, this increases the chance that operators will trust unsafe setup steps and mishandle more sensitive credentials in adjacent high-risk operations.
No suspicious patterns detected.