T08 · Insecure Dependencies
- Location
README.md:56- Finding
Unpinned Third-Party Skill Dependencies
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is not clearly malicious, but it can publish to connected social accounts automatically despite settings that imply draft-only or manual control.
Install only if you are comfortable giving this workflow publishing access to real Xiaohongshu and WeChat accounts. Before enabling it, pin and verify dependency skills, store credentials outside plaintext configs, disable schedules and webhooks by default, and require human preview/approval before every publish action.
README.md:56Unpinned Third-Party Skill Dependencies
workflow.json:112Scheduled Workflow Can Bypass the Disabled Auto-Publish Setting
声明描述的核心能力是“生成多平台内容并自动分发”,即内容改写/生成与发布分发流程。而代码仅是一个 discovery.sh 热点发现脚本:接收主题词,调用 agent-reach 在小红书、微博、知乎执行搜索,将结果输出到本地文件,并做简单汇总。它没有实现任何内容生成、转换、排版、发布、分发或调度逻辑。虽然热点发现可能是内容矩阵工作流的辅助步骤,但该代码片段的主要目的与声明的主要目的存在明显差异,因此应判定为描述与实际行为不匹配。
The README presents all user-facing instructions and examples exclusively in Chinese, which can amount to a language-policy issue when no user opt-in or locale limitation is stated. The policy allows fixed-language behavior only when the skill offers a language choice or clearly documents a justified regional constraint, neither of which appears here.
The trigger scope is effectively unspecified, while the examples are broad, everyday requests such as generating and distributing topical content. In an agent environment, vague triggers can cause unintended invocation of a skill that performs external searches and may lead to publication actions, increasing the risk of accidental data disclosure or unauthorized posting.
The skill is designed to publish to external platforms using stored account credentials, but the description does not prominently warn users that it can perform outbound posting on their behalf. Without explicit user-facing notice and confirmation, a user may invoke the skill expecting drafting assistance while the agent proceeds to search, transform, and publish content through connected accounts.
The configuration embeds highly sensitive authentication material such as web session cookies and WeChat app credentials, but the document does not include secure-handling guidance or privacy warnings. If users store these values insecurely, share configs, or logs expose them, attackers could hijack platform accounts, publish unauthorized content, or access associated account data.
The file uses Chinese-only natural-language labels and config values throughout, and explicitly fixes the timezone to Asia/Shanghai. This indicates a Chinese locale assumption without any visible opt-in, alternative locale support, or justification that the skill is region-specific.
This shell script uses Chinese in its title, status messages, and error messages throughout, with no indication that the user can choose another language or that the skill is intentionally limited to a Chinese-speaking or region-specific context. That creates a natural-language locale policy issue under the rule for forced language without user opt-in.
The script performs live publishing to external platforms as soon as DRY_RUN is not set to true, without any interactive confirmation, approval gate, or secondary safeguard. In a content-distribution skill, this increases the chance of accidental or unauthorized publication caused by operator error, bad upstream input, or automation misuse, potentially exposing sensitive, incorrect, or premature content to public audiences.
The workflow defines a cron trigger for daily automatic publishing across external platforms, but the file provides no explicit approval gate, user warning, or restriction before posting. In a content-publishing skill, unattended scheduled execution materially increases the risk of accidental spam, policy-violating posts, reputational damage, or unintended publication of generated content at scale.
The webhook trigger allows remote initiation of a workflow that includes external publishing actions, yet the configuration shows no visible authentication, authorization, confirmation, or warning controls. In this skill’s context, remote triggering is especially risky because it can cause unauthorized posting to multiple accounts, turning an API exposure or misconfiguration into immediate public-facing impact.
The script's comments and user-visible status/error messages are written in Chinese throughout, which imposes a specific language on all users. The file does not provide any language selection, fallback, or documented justification that the skill is intended only for a Chinese-speaking or region-specific context.
This markdown template mandates Chinese-language output throughout the skill content, including headings, structure, and example text. The file does not indicate that language selection is optional or user-configurable, which can conflict with language/locale choice policies when no opt-in is provided.
The description forces a specific language presentation in the manifest, and other visible strings in the file are also Chinese-only. There is no indication that the skill is limited to Chinese-speaking users or that users can opt into this locale, which may conflict with language-choice policy expectations.