T09 · Insecure Skill Coding Practices
- Location
deepseek-api-guide.md:47- Finding
API integration templates encourage hardcoded credentials
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a disclosed DeepSeek API documentation skill with no executable install behavior, but users should handle API keys and sensitive prompt data carefully.
Install only if you want Chinese-language DeepSeek API guidance. Do not paste real API keys into source code or shell history, and do not send sensitive customer, regulated, proprietary, or secret data to DeepSeek unless your organization has approved that use.
deepseek-api-guide.md:47API integration templates encourage hardcoded credentials
The primary descriptive text is presented in Chinese, and the README does not indicate that the skill is intentionally limited to Chinese-speaking users or provide an English/locale choice. Under the stated policy, forcing a specific language without user opt-in is a natural-language policy concern.
The activation conditions are broad enough to match many ordinary AI/API-related requests, which can cause this skill to activate when the user did not specifically ask for DeepSeek-focused guidance. Over-broad activation increases the chance of context hijacking, irrelevant vendor steering, and unintended disclosure or processing of user context under the wrong skill.
The guidance recommends placing a long knowledge base into the system prompt for caching, but it does not warn that this may send proprietary, regulated, or personal data to a third-party API. In a cost-optimization skill, that omission is meaningful because readers are encouraged to maximize reuse of large prompt prefixes, which can normalize bulk external data transfer without data-classification checks.
The optimization example hard-codes an instruction to translate content into Chinese, and the surrounding document is entirely written as prescriptive guidance in Chinese without any opt-in or locale justification. Per the policy, forcing a specific language without user choice can be a natural-language locale violation.
The example sends full conversation history to an external API for summarization without warning about privacy, confidentiality, or retention risks. This is dangerous because conversation histories often contain credentials, personal data, or sensitive business context, and the cost-saving framing may incentivize sending everything rather than minimizing or filtering data.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
POST https://api.deepseek.com/chat/completions
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
POST https://api.deepseek.com/chat/completions
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
POST https://api.deepseek.com/chat/completions
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
POST https://api.deepseek.com/chat/completions
This markdown file includes multiple examples that send user-provided message content to the DeepSeek API, but the surrounding documentation does not warn users that prompts and conversation data will be transmitted to an external service. For markdown files, omission of warnings about behaviors affecting user data or privacy is in scope.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
);
### curl
```bash
curl https://api.deepseek.com/chat/completions \
The entire skill content, including headings, guidance, and examples, is presented only in Chinese, with no indication that users can choose another language or that the skill is intentionally limited to a Chinese-speaking context. Under the policy, forcing a specific language without user opt-in is a natural-language locale violation.
The document states '中文场景用中文' and provides examples directing the assistant to answer in Chinese as the preferred/default behavior. This is a natural-language locale policy constraint without any indication of user opt-in or alternative language selection.
The guidance recommends using Chinese system prompts for Chinese scenarios without an explicit user opt-in or preference check. While not directly enabling code execution or data exfiltration, it can override user expectations, change instruction semantics, and create policy or usability issues if the system prompt language is silently altered.
A language or locale policy issue applies when a skill forces a specific language without user opt-in. This guide is entirely Chinese-language and does not indicate that Chinese is optional or that the document is specifically intended for a Chinese-only audience.
No suspicious patterns detected.