T09 · Insecure Skill Coding Practices
- Location
main.py:58- Finding
Arbitrary File Creation Through an Unsanitized Keyword
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This package is presented as a YouTube Shorts generator, but its code and manifest actually implement a Chinese ecommerce product-selection and listing workflow with unsafe file and network handling.
Review this skill carefully before installing. Do not provide marketplace credentials or sensitive product data unless the publisher aligns the user-facing description, manifest, and code, adds explicit approval gates for any publishing/listing action, and fixes the unsafe file and image-download handling. Treat any generated compliance or success result as advisory only until the workflow performs real checks and verifies real outputs.
main.py:58Arbitrary File Creation Through an Unsanitized Keyword
utils.py:49Server-Side Request Forgery Through Unrestricted Image URLs
utils.py:49Unbounded Download Buffering and Missing Image Content Validation
main.py:198Compliance Workflow Unconditionally Approves Unexamined Content
steps/publish.py:34Generation and Publishing Functions Return Fabricated Success Results
The description promises fully automated generation of AI video, TTS, editing, thumbnailing, and SEO copy with a simple trigger, but the file provides only high-level claims and dependency notes. In an agent setting, such exaggerated capability claims can socially engineer users into sharing topics, API keys, or trusting output handling without understanding that steps may be incomplete, outsourced, or manually approximated.
The description promises fully automated generation of AI video, TTS, editing, thumbnailing, and SEO copy with a simple trigger, but the file provides only high-level claims and dependency notes. In an agent setting, such exaggerated capability claims can socially engineer users into sharing topics, API keys, or trusting output handling without understanding that steps may be incomplete, outsourced, or manually approximated.
The description promises fully automated generation of AI video, TTS, editing, thumbnailing, and SEO copy with a simple trigger, but the file provides only high-level claims and dependency notes. In an agent setting, such exaggerated capability claims can socially engineer users into sharing topics, API keys, or trusting output handling without understanding that steps may be incomplete, outsourced, or manually approximated.
The description promises fully automated generation of AI video, TTS, editing, thumbnailing, and SEO copy with a simple trigger, but the file provides only high-level claims and dependency notes. In an agent setting, such exaggerated capability claims can socially engineer users into sharing topics, API keys, or trusting output handling without understanding that steps may be incomplete, outsourced, or manually approximated.
The description promises fully automated generation of AI video, TTS, editing, thumbnailing, and SEO copy with a simple trigger, but the file provides only high-level claims and dependency notes. In an agent setting, such exaggerated capability claims can socially engineer users into sharing topics, API keys, or trusting output handling without understanding that steps may be incomplete, outsourced, or manually approximated.
The description promises fully automated generation of AI video, TTS, editing, thumbnailing, and SEO copy with a simple trigger, but the file provides only high-level claims and dependency notes. In an agent setting, such exaggerated capability claims can socially engineer users into sharing topics, API keys, or trusting output handling without understanding that steps may be incomplete, outsourced, or manually approximated.
The description promises fully automated generation of AI video, TTS, editing, thumbnailing, and SEO copy with a simple trigger, but the file provides only high-level claims and dependency notes. In an agent setting, such exaggerated capability claims can socially engineer users into sharing topics, API keys, or trusting output handling without understanding that steps may be incomplete, outsourced, or manually approximated.
The description promises fully automated generation of AI video, TTS, editing, thumbnailing, and SEO copy with a simple trigger, but the file provides only high-level claims and dependency notes. In an agent setting, such exaggerated capability claims can socially engineer users into sharing topics, API keys, or trusting output handling without understanding that steps may be incomplete, outsourced, or manually approximated.
The description promises fully automated generation of AI video, TTS, editing, thumbnailing, and SEO copy with a simple trigger, but the file provides only high-level claims and dependency notes. In an agent setting, such exaggerated capability claims can socially engineer users into sharing topics, API keys, or trusting output handling without understanding that steps may be incomplete, outsourced, or manually approximated.
The description promises fully automated generation of AI video, TTS, editing, thumbnailing, and SEO copy with a simple trigger, but the file provides only high-level claims and dependency notes. In an agent setting, such exaggerated capability claims can socially engineer users into sharing topics, API keys, or trusting output handling without understanding that steps may be incomplete, outsourced, or manually approximated.
The skill metadata advertises YouTube Shorts video automation, but the file implements a Chinese-language ecommerce product-selection and listing workflow. This scope mismatch is dangerous because users and higher-level agents may grant permissions, provide inputs, or trust outputs appropriate for video creation while the code instead drives commercial research and publication-related actions outside the declared purpose.
The workflow includes a publication/listing phase that exceeds the declared scope of 'ready-to-upload 15-60 second vertical video' generation. Hidden or undeclared publishing capabilities materially increase operational risk because an orchestrator or user may invoke the skill expecting content generation only, while it prepares commercial posting actions and related assets.
The manifest metadata materially conflicts with the stated skill purpose: the reviewed skill is presented as YouTube Shorts automation, but the name and description define a Chinese ecommerce short-video product-selling workflow. This kind of scope mismatch is dangerous because it can conceal undeclared capabilities, mislead reviewers and users, and enable a bait-and-switch installation of a different automation surface than expected.
The dependency set includes ecommerce and marketplace integrations such as product data, listing APIs, and Xiaohongshu platform support that are not justified by a YouTube Shorts creation workflow. Unnecessary commercial and publishing capabilities expand the attack surface and could be abused for unauthorized product research, listing, cross-platform posting, or exfiltration of business data under the cover of a media-generation skill.
This file implements automated e-commerce product listing behavior even though the skill is ներկայացված as a YouTube Shorts automation workflow. That capability mismatch is dangerous because it introduces undeclared external-publishing behavior and a path to move user-supplied product/media data to third-party marketplaces under a misleading skill identity, which is a strong indicator of hidden or unauthorized functionality.
The file implements product-market research for dropshipping goods, including planned integration with multi-platform product search, filtering for dropshipping, and returning supplier contact data, which is unrelated to the declared YouTube Shorts automation purpose. This capability mismatch is dangerous because it can hide unauthorized commerce or lead-generation behavior inside a media-creation skill, increasing the risk of deceptive scope expansion and unexpected data handling.
The README promotes fully automated creation of upload-ready videos, thumbnails, and SEO metadata without any caution about copyright ownership of generated assets, factual accuracy of scripts, or compliance with YouTube/platform rules. In this context, users may reasonably rely on the automation as safe for direct publishing, increasing the risk of misinformation, infringing content, deceptive metadata, or policy-violating uploads at scale.
The skill advertises capabilities that inherently require filesystem access, environment/API key access, and likely network calls, but it declares no explicit tool scope or permission boundaries. In an agent ecosystem, this creates an under-specified trust boundary and can allow broader-than-expected access or make review and consent ineffective.
The skill explicitly requires external AI video generation services and likely TTS services, yet it does not warn users that their topics, prompts, scripts, or other content may be transmitted to third parties. For a content-generation workflow, that omission is significant because users may unknowingly share proprietary, sensitive, or unpublished material with external vendors.
The file docstring identifies the module as "short-video-ecommerce" and describes "短视频带货全流程自动化" (short-video e-commerce full-process automation), which conflicts with the manifest's YouTube Shorts creation workflow and the exported class name ShortVideoEcommerceSkill. This is an active documentation-level contradiction about the skill's intended function, not merely an omitted detail.
The module docstring defines the skill name, trigger phrase, and workflow entirely in Chinese, including the activation phrase at L005, with no indication that other languages are supported. This is a natural-language policy concern because it imposes a specific language/locale on users without an explicit opt-in or alternative.
The docstring for step6_publish states that the function performs one-click publishing to an ecommerce platform. The actual code merely writes publication guidance to a text file and returns {'auto_publish': False}, which directly contradicts the documented intent.
The manifest description is entirely in Chinese and presents the skill as targeting Chinese platforms and workflows, but it does not state that the skill is region-specific or offer a language/locale choice. This can violate language/locale policy because the skill appears to impose a specific language context by default rather than documenting opt-in or justification.
The module docstring and all user-facing report content are written exclusively in Chinese, indicating the skill is designed to operate in a single language. Under the policy, language-specific behavior should offer user opt-in or clearly document a justified regional constraint, which is not present here.
The module docstring states the step is for generating copywriting scripts entirely in Chinese, and the templates and output labels are also fixed in Chinese. This imposes a specific language/locale behavior without any indication that the user can choose another language or opt in to Chinese output.
No suspicious patterns detected.