T08 · Insecure Dependencies
- Location
SKILL.md:72- Finding
Unpinned Third-Party Dependency Installation
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill mostly matches its image-generation purpose, but it needs review because it stores and uses an AI Hive API key and can send that key to an arbitrary configured API endpoint.
Review this skill before installing if you will use a real AI Hive API key. Use the default AI Hive endpoint unless you intentionally trust a custom endpoint, protect ~/.ai-hive/config.json from modification, avoid uploading non-image or sensitive files, and consider pinning dependencies before installation.
SKILL.md:72Unpinned Third-Party Dependency Installation
scripts/imagegen.py:91Unrestricted Base URL Override Can Expose API Credentials
Video generation is a materially broader capability than the declared image-only livestream asset generation and permits uploading image, video, and audio inputs plus retrieving generated media. This unnecessary capability expansion significantly increases misuse potential, operational cost exposure, and the chance that an agent can perform actions outside the approved scope.
The skill invokes shell commands, installs a package, and uses a Python script that likely performs file, environment, and network operations, but it declares no explicit tool scope or permission boundaries. This creates unnecessary privilege exposure: an agent may grant or assume broader capabilities than needed, increasing the blast radius if the script is modified, compromised, or triggered in an unexpected context.
The manifest description says to use this skill for a long list of generic livestream-image scenarios spanning multiple platforms and materials, but it does not define clear trigger boundaries or exclusions. In a manifest file, this breadth can make invocation conditions ambiguous and increase unintended activation for ordinary image-design requests.
The skill text predominantly requires Chinese-language usage and examples, yet it is described for platforms like TikTok Live and Amazon Live that may involve users in other locales. Because no opt-in or language-selection guidance is provided, this can impose a specific language/locale on users without explicit choice.
The file presents itself as a generic AI utility supporting chat, image, video, model enumeration, uploads, and task polling, while the declared skill is narrowly scoped to GPT Image 2 livestream-commerce image generation. This scope mismatch increases the attack surface and can mislead reviewers or orchestrators into granting a narrowly intended skill far broader capabilities than expected.
This Python skill’s docstring and CLI-facing help/messages are written in Chinese, establishing a fixed language/locale experience without any opt-in or alternative. The policy requires flagging language or locale constraints when the skill forces a specific language without user choice, and no multilingual option or justification is present in the file.
Exposing text chat in an image-generation skill violates least privilege and enables arbitrary prompt forwarding to a text model unrelated to the skill's stated purpose. In an agent environment, that broadens what the skill can do beyond user expectations and may be abused for unintended data handling or policy bypass via an overly capable auxiliary interface.
This markdown file contains user-facing natural language almost exclusively in Chinese, which can constitute a language/locale policy issue when no opt-in or justification is provided. The file does not state that the skill is region-specific or that Chinese is an intentional locale constraint.
The example API key value uses Chinese text ('请替换为你的APIKey') as an instruction embedded directly in the configuration. This imposes a specific language in user-facing content without any indication that language selection is optional or region-specific.
User-info and model-enumeration endpoints are outside the stated purpose of generating livestream images and reveal account metadata and available backend capabilities. While lower severity than chat/video exposure, they still expand reconnaissance value and break the principle of minimal disclosure for a narrowly scoped skill.
No suspicious patterns detected.