T08 · Insecure Dependencies
- Location
SKILL.md:58- Finding
Unpinned Runtime Dependency Installation
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a disclosed AI Hive ad-image generator; its main risks are normal API-key storage, user-selected image uploads, and an unpinned dependency install, not hidden or destructive behavior.
Before installing, use an isolated environment if possible, consider pinning `requests`, and only provide reference images and an AI Hive API key you are comfortable sending to AI Hive and its upload/download storage flow. Expect the init command to open a browser and store the API key locally in `~/.ai-hive/config.json`.
SKILL.md:58Unpinned Runtime Dependency Installation
The skill invokes a Python script with network, shell, file, and environment access but does not declare any explicit tool scope or permissions boundary. That mismatch can cause an agent runtime to grant broader capabilities than a reviewer or user expects, increasing the risk of unintended file access, secret exposure, or outbound requests if the script is modified or misused.
The manifest description and main instructions are written as mandatory Chinese-language guidance, while also embedding English trigger terms, but nowhere state that the skill is China-specific or that users may choose another language. This can violate language/locale policy because it effectively constrains interaction language without explicit opt-in or documented justification.
The module docstring and user-facing CLI guidance are written entirely in Chinese, and the skill does not provide any opt-in or fallback for other languages. This creates a natural-language policy concern because the skill implicitly forces a specific language/locale on all users.
The skill’s stated purpose is generating testable ad images via AI Hive, but the init flow also launches a browser to a chat page and appends from=cli-skill&skill=... for backend attribution. Opening a browser for API key setup is understandable, but adding tracking-style attribution metadata is not necessary to the core ad-image function described in the manifest.
No suspicious patterns detected.