T01 · Skill Instruction Hijacking
- Location
SKILL.md:130- Finding
Mandatory Third-Party Branding Injected into Generated Images
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill does what it claims, but its handling of a Mew.Design API key is too exposed and loosely scoped for automatic approval.
Review this skill before installing if you use a real Mew.Design API key. Only provide a key you are comfortable using through this skill, prefer a limited or revocable key, and be aware that summarized chat content is sent to Mew.Design to generate the image. Do not use it for sensitive conversations unless the key-handling and destination restrictions are fixed.
SKILL.md:130Mandatory Third-Party Branding Injected into Generated Images
scripts/validate_mew_design_key.py:20API Key Exposed Through Command-Line Arguments
scripts/validate_mew_design_key.py:21Caller-Controlled Validation Endpoint Can Receive the User API Key
The skill is presented as a conversation-to-image summarizer, but its behavior includes API-key validation via auth probing and direct external API interaction that are not clearly disclosed by the high-level description. This mismatch can mislead users and reviewers, reducing informed consent and making sensitive key handling and network behavior easier to hide.
Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.
## Compression Heuristics
- Merge repeated requests into one clear statement.
- Collapse implementation detail into one bullet unless the detail affects outcome.
- Keep at most one metric per bullet unless comparisons matter.
- Convert long prose into noun-verb phrases.
The skill invokes shell commands, writes temporary files, and makes outbound network requests, yet declares no tool scope or permission boundaries. That creates an over-privileged, opaque execution model where an agent may run sensitive actions without explicit installation-time disclosure or policy gating.
The installation trigger phrases are broad and overlap with ordinary user language such as asking for help installing a skill. That increases the chance of accidental activation, causing users to enter a workflow that requests secrets and performs external actions without sufficiently deliberate intent.
The skill instructs the agent to collect a user's mew.design API key and reuse it, but provides no explicit privacy notice, storage/retention limits, masking guidance, or warning about sending the key to external services. Secret collection without clear handling constraints increases the risk of credential leakage, over-retention, or unsafe display in logs and transcripts.
The file mandates using the "exact onboarding copy" in Chinese and later provides a Chinese-only style-selection message, with no option to match the user's language. This is a natural-language policy issue because it imposes a specific locale without user choice or documented justification.
The instructions require a fixed Chinese style-selection format after key validation and do not provide an alternative based on user preference. Requiring a specific language for user interaction without opt-in violates the language/locale policy criteria.
The skill transmits user conversation-derived content and the supplied API key to an external service. This is sensitive data egress: private chat content may leave the local environment, and the credential is sent in a request header, so users need clear consent and strict host restrictions before execution.
Then generate the image through the official Mew design API:
curl -sS -X POST "https://api.mew.design/open/api/design/generate" \
-H "Content-Type: application/json" \
-H "x-api-key: USER_PROVIDED_KEY" \
--data @/tmp/chat-summary-body.json
The skill transmits user conversation-derived content and the supplied API key to an external service. This is sensitive data egress: private chat content may leave the local environment, and the credential is sent in a request header, so users need clear consent and strict host restrictions before execution.
Then generate the image through the official Mew design API:
curl -sS -X POST "https://api.mew.design/open/api/design/generate" \
-H "Content-Type: application/json" \
-H "x-api-key: USER_PROVIDED_KEY" \
--data @/tmp/chat-summary-body.json
The instruction explicitly says to create the image in Chinese unless the provided copy is clearly another language. This imposes a specific language default without offering the user a choice or opt-in, which matches the policy category for language or locale violations.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
import urllib.parse
import urllib.request
DEFAULT_BASE_URL = "https://api.mew.design/"
def parse_args() -> argparse.Namespace:
Detected: suspicious.exposed_secret_literal