T09 · Insecure Skill Coding Practices
- Location
scripts/imagegen.py:91- Finding
Arbitrary API base URL can receive the AI-HIVE bearer credential in imagegen.py
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is mostly a disclosed AI-HIVE media workflow, but its scripts handle API credentials and downloaded files in ways that deserve careful review before installation.
Install only if you trust the AI-HIVE workflow and need this Chinese-language GEO/AEO plus media-generation integration. Keep the API key low-privilege and revocable, avoid setting AI_HIVE_BASE_URL or --base-url to anything except the official AI-HIVE endpoint, do not reuse sensitive production keys, and choose output directories where accidental overwrite would not be damaging.
scripts/imagegen.py:91Arbitrary API base URL can receive the AI-HIVE bearer credential in imagegen.py
scripts/videogen.py:91Arbitrary API base URL can receive the AI-HIVE bearer credential in videogen.py
scripts/imagegen.py:400Server-controlled task metadata can cause output-directory traversal in imagegen.py
scripts/videogen.py:400Server-controlled task metadata can cause output-directory traversal in videogen.py
Undeclared API key initialization and storage, account lookup, wallet balance retrieval, and generic generation capabilities materially expand the privilege and privacy footprint beyond what the title and summary suggest. Hidden or under-disclosed credential and account operations can cause users to reveal sensitive tokens or let the skill persist secrets locally without informed consent.
Undeclared API key initialization and storage, account lookup, wallet balance retrieval, and generic generation capabilities materially expand the privilege and privacy footprint beyond what the title and summary suggest. Hidden or under-disclosed credential and account operations can cause users to reveal sensitive tokens or let the skill persist secrets locally without informed consent.
Undeclared API key initialization and storage, account lookup, wallet balance retrieval, and generic generation capabilities materially expand the privilege and privacy footprint beyond what the title and summary suggest. Hidden or under-disclosed credential and account operations can cause users to reveal sensitive tokens or let the skill persist secrets locally without informed consent.
The skill advertises executable scripts and API-based workflows that imply access to shell, network, filesystem, and environment variables, but it does not declare any explicit tool scope or permission boundaries. This creates an avoidable trust gap: users and hosting platforms cannot easily tell what capabilities the skill may exercise, increasing the chance of overbroad execution or misuse of local secrets and files.
The summary and description say the skill is '适合搜索' a long list of terms including very broad keywords like '短剧', '漫剧', 'GEO', and 'AEO'. In a markdown skill description, this makes the trigger scope ambiguous because it does not distinguish between when the skill should activate versus when those common topic words are merely mentioned in ordinary conversation.
The metadata sets the language to 'zh-CN', and the document does not state that users may choose another language or that the skill is intentionally limited to a China-specific compliance or regional workflow. Under the policy, forcing a specific language or locale without user opt-in is a natural-language policy violation.
The skill enables implicit invocation with no visible trigger constraints, which can cause the agent to activate this skill in overly broad contexts. Because this skill is oriented toward planning, generation, and workflow execution, unintended activation could expose user data to the skill prompt path, cause undesired actions, or override a more appropriate skill selection.
The module docstring and client implement generic text chat, image generation, video generation, model querying, media upload, and task polling. The built skill configuration at L775-L776 brands this artifact as a GPT Image 2 picture generation/editing skill, so bundling unrelated text-chat and video-generation behavior indicates a broader capability set than the skill claims.
The top-level docstring presents the skill description and usage guidance entirely in Chinese, which effectively forces a specific language for user-facing interaction. Under the policy, locale constraints should either be optional for the user or explicitly justified as region-specific, neither of which is stated here.
The manifest describes a narrowly branded skill for GEO/AEO growth support using image/video models, and this file's embedded skill config further presents itself as a GPT Image 2 image generation/editing skill. However, the underlying script includes broader operational capabilities such as API-key setup and task/media management that go beyond simply generating or editing images for the declared skill purpose.
This code file contains natural-language user-facing descriptions entirely in Chinese, including the module docstring and CLI help text, but does not indicate that the skill is Chinese-only or provide an opt-in choice of language. Under the policy, forcing a specific language without user choice is a natural-language policy violation.
The skill metadata presents a GEO+AEO/brand-growth planning expert, but this file implements a full media-generation/upload/download client with task polling and model routing. That capability mismatch is dangerous because users or orchestrators may grant or invoke the skill under a lower-risk expectation, while it can perform external network operations, upload local files, and download generated content to disk.
The display name, description, and default prompt are written entirely in Chinese, which suggests a fixed language presentation for users. There is no indication that the user can opt into another language or that the skill is intentionally restricted to a Chinese-speaking context.
The manifest emphasizes brand AI search growth strategy and content/task decomposition, with AI-HIVE mentioned as a unified way to use media models. Endpoints for querying wallet/user account information and listing arbitrary available models are generic platform-administration capabilities that are not clearly necessary for the stated expert/advisory purpose.