T09 · Insecure Skill Coding Practices
- Location
index.js:320- Finding
API Key Exposed Through Recharge URL and Chat Output
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill has a coherent GIF-reaction purpose, but it handles its hosted-service API key too loosely, including a path that can print the full key into chat and URLs.
Install only if you are comfortable with a hosted reaction service receiving short, non-sensitive reaction metadata and storing a local API key. Avoid passing secrets or private conversation summaries in metadata, and treat any recharge output carefully because this version can reveal the full API key in chat and URLs.
index.js:320API Key Exposed Through Recharge URL and Chat Output
index.js:334Unrestricted Metadata Transmission and Hosted API Endpoint Override
index.js:181Locally Stored API Key Lacks Explicit Restrictive File Permissions
Referenced artifact was not completely inspected
Import from `index.js` and call one of these functions:
Referenced artifact was not completely inspected
Import from `index.js` and call one of these functions:
The publish instructions use npx clawhub without pinning an exact package version, so anyone following the documented release process may execute whatever version is currently served by the registry at publish time. If the package is compromised, typosquatted, or a newer malicious version is introduced, this can lead to arbitrary code execution on the publisher's machine or manipulation of the published skill metadata.
The skill persists an API key to localStorage in browser contexts or to a plaintext JSON file in Node contexts without any consent prompt, warning, or protection mechanism. This creates credential exposure risk through XSS, other local users/processes, backups, logs, or accidental file disclosure, and the key appears to grant access to a third-party hosted service.
Several user-visible messages are hardcoded in Chinese, such as the initialization status text, recharge text, and default captions. The file does not offer locale selection or document that the skill is intentionally region-specific, which conflicts with the policy against forcing a language without user opt-in.
The skill packages metadata derived from user messages, replies, tool summaries, and conversation summaries into a payload and sends it to a remote host for reaction generation, but there is no user-facing disclosure, consent, or minimization control. Because these fields can contain sensitive conversational or system data, this can result in unintended exfiltration to an external domain.
The manifest presents the skill as a simple GIF-reaction add-on, but it also declares hosted API usage and automatic API key registration. This mismatch is security-relevant because it can mislead users and reviewers about hidden networked behavior, account provisioning, and data exchange with a remote service.
Automatic API key registration is not obviously necessary for a skill whose stated function is adding occasional GIF reactions. Unnecessary credential provisioning expands attack surface, can create opaque remote accounts, and may enable unexpected tracking or later abuse if the remote service is compromised or behaves differently than users expect.
The manifest indicates automatic API key registration and local storage of the resulting key, but it does not warn users about credential transmission, storage, or handling. This lack of transparency increases the risk of users unknowingly sending identifiers to a third party and storing secrets locally without understanding retention, protection, or revocation implications.
The package description says this is a skill for hosted GIF reactions with API key registration and beta access, but the package name and homepage indicate a temperature-themed skill. The keywords also reinforce the GIF/reaction purpose rather than temperature functionality, creating a clear semantic mismatch in the declared intent of the skill.
This file includes user-facing strings such as payment labels and instructions entirely in Chinese, and the tests assert those exact values. Because there is no indication here of user opt-in, language selection, or a documented region-specific constraint, this reflects a natural-language locale policy issue under the requirement not to force a specific language without user choice.
Several assertions require Chinese captions and messaging for generated markdown output, which indicates the skill behavior is expected to be Chinese-only. In the absence of any visible opt-in, locale negotiation, or documentation that the skill is region-specific, this is a natural-language policy violation.
These tests validate reaction classification solely against Chinese user messages and assistant replies, suggesting the skill may be designed around a single forced language. Without evidence of optional language handling or documented locale limits, this creates a policy concern about forcing a locale without user choice.