T09 · Insecure Skill Coding Practices
- Location
SKILL.md:18- Finding
Publicly Documented Shared API Credential
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill performs the advertised mind-map generation task, but it asks users to use a shared API key and sends user text plus that key to an under-disclosed HTTP service.
Review before installing. Do not submit confidential, proprietary, regulated, or secret-bearing text unless you control and trust the service listening on 127.0.0.1:8000. Replace the shared trial key with a unique key, and prefer an authenticated HTTPS or protected local IPC setup before routine use.
SKILL.md:18Publicly Documented Shared API Credential
scripts/generate.mjs:38Sensitive Input and API Credential Sent to an Unauthenticated Plaintext Local Service
The skill declares code-related capabilities through required binaries and environment variables, and it appears to rely on an external API, but it does not explicitly declare tool scope such as allowed tools or permissions. This creates unnecessary ambiguity about what execution and network access the skill may use, making review and policy enforcement harder and increasing the risk of unintended data access or outbound transmission.
The manifest description and instructions are entirely in Chinese and present the skill as operating in that language without any indication that users may choose another language or that the locale restriction is required. This can violate language/locale policy when no opt-in or justification is provided.
The skill asks for an API key and takes arbitrary input text, but it does not disclose that the text will be sent to an external service for processing. This omission is dangerous because users may pass sensitive, proprietary, or regulated content under the false assumption that processing is local, resulting in unconsented data disclosure.
The documentation instructs users to set a hardcoded default trial API key in an environment variable, which is a major red flag because embedded credentials encourage secret reuse and may route requests through an untrusted shared account. Hardcoded or shared API keys can enable unauthorized service use, abuse attribution confusion, and possible exfiltration of user-submitted content to a third party without proper ownership or consent.
The script includes user-facing comments and error/output strings in Chinese, such as the prompt at L24 and status text at L56/L62, without offering any locale or language selection. This creates a natural-language policy issue because it imposes a specific language on users without documented opt-in or justification.
The script transmits the full user-provided text to an external service for processing, but the skill description only presents this as a local mind-map generation capability. This creates a data disclosure and trust-boundary issue because users may provide sensitive text without realizing it is being forwarded off-process to another server.
The request sends both the user's full text and an API key to a server without any user-facing warning or disclosure, preventing informed consent for data sharing. In addition, the endpoint uses plain HTTP, so if this is changed from localhost to a remote host as the comment suggests, the payload and credential could be exposed in transit.
The skill requires an API key from the environment even though that capability is not disclosed in the manifest, which weakens transparency around credential use. While the code does not itself exfiltrate arbitrary environment data, it does handle a secret and sends it in a request header to a service that users are not clearly informed about.