T09 · Insecure Skill Coding Practices
- Location
scripts/videogen.py:91- Finding
Bearer Credential Disclosure Through an Unrestricted API Base URL
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is mostly aligned with AI-HIVE video generation, but it needs Review because its API key can be sent to a user-configured API endpoint.
Install only if you trust AI-HIVE and are comfortable storing an API key locally. Do not use --base-url, AI_HIVE_BASE_URL, or config.json values from anyone else, and rotate the API key if it may have been used with an untrusted endpoint. Expect uploads of selected media and possible billable generation after confirmation.
scripts/videogen.py:91Bearer Credential Disclosure Through an Unrestricted API Base URL
scripts/videogen.py:7Unpinned Runtime Dependency Installation
The finding suggests the skill presents itself as a narrowly focused demo-video generator but also includes broader capabilities such as generic chat/image generation, account or wallet access, model inventory access, and local credential setup. When a skill has materially broader access than declared, it increases the risk of credential exposure, overcollection of user data, unintended account actions, and policy bypass through a misleadingly narrow description.
The finding suggests the skill presents itself as a narrowly focused demo-video generator but also includes broader capabilities such as generic chat/image generation, account or wallet access, model inventory access, and local credential setup. When a skill has materially broader access than declared, it increases the risk of credential exposure, overcollection of user data, unintended account actions, and policy bypass through a misleadingly narrow description.
The finding suggests the skill presents itself as a narrowly focused demo-video generator but also includes broader capabilities such as generic chat/image generation, account or wallet access, model inventory access, and local credential setup. When a skill has materially broader access than declared, it increases the risk of credential exposure, overcollection of user data, unintended account actions, and policy bypass through a misleadingly narrow description.
The skill advertises executable workflows and includes shell commands, network access, file operations, and environment variable handling, but it does not declare any tool scope such as permissions or allowed-tools. In an agent environment, this weakens least-privilege boundaries and can lead to unintended execution of filesystem, shell, or network actions beyond what reviewers or orchestrators expect.
The invocation description and surrounding user-facing content are written entirely in Chinese and position the skill for Chinese-language requests, but there is no explicit opt-in or statement that other languages are supported. Under the policy for natural-language constraints, forcing a specific language without user choice can be a locale/language policy violation.
The natural-language instruction explicitly says to turn the request into a production-ready Chinese workflow, which imposes a language requirement regardless of user preference. This is a language/locale policy concern because the file does not offer a language choice or document a justified region-specific constraint.
subprocess module calls execute external commands. Without careful input validation, this enables command injection.
def run(args: list[str]) -> None:
print(" ".join(args))
subprocess.run(args, check=True)
def main() -> None:
The file presents itself as a specialized tabletop product demo video skill, but actually embeds a broad, reusable AI Hive client supporting chat, image, video, model enumeration, uploads, and task polling. This capability mismatch increases attack surface and violates least privilege: a caller or wrapper expecting a constrained video skill could unintentionally gain access to unrelated AI operations and broader data handling paths.
The module documentation explicitly describes a general AI capability tool, which contradicts the claimed specialized skill identity. This kind of deceptive or misleading packaging is dangerous because reviewers, orchestrators, or users may grant permissions based on the narrower description while the code actually supports far broader operations.
This code file contains natural-language user-facing descriptions that default to Chinese, including the module docstring and later CLI help text. Under the policy, forcing a specific language without user opt-in is a natural-language policy violation unless the locale constraint is explicitly documented and justified.
Across the script, user-visible errors, prompts, argparse help strings, and progress messages are presented in Chinese only. Because the skill does not offer a language/locale choice or justify a Chinese-only scope, this violates the language/locale policy for natural-language content in code files.
Arbitrary text chat support is unjustified in a narrowly scoped tabletop product demo video skill and enables unrestricted prompting against external models. In skill ecosystems, this can be abused to bypass higher-level policy constraints, process unrelated sensitive text, or turn a specialized media tool into a general-purpose LLM proxy.
Standalone image generation is broader than the declared purpose of a tabletop product demo video skill and unnecessarily widens model access and output capabilities. This makes the skill a multipurpose content-generation gateway rather than a constrained video workflow, increasing misuse potential and policy bypass risk.
The file’s natural-language description and CLI description are entirely in Chinese, and there is no indication that the user can choose another language or that the skill is intentionally restricted to a Chinese-speaking context. Under the stated policy, forcing a specific language without user opt-in is a natural-language policy concern.
Exposing user-info and wallet balance lookup is unrelated to generating tabletop product demo videos and creates unnecessary access to account metadata. While not direct code execution, it expands sensitive surface area and can leak billing or account details to contexts that only needed media generation.