T01 · Skill Instruction Hijacking
- Location
scripts/hashtag_generator.py:34- Finding
Unrelated Third-Party Brand Injection into User-Generated Marketing Content
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a mostly coherent marketing toolkit, but it silently adds unrelated company branding to generated content and under-discloses external AI/file handling risks.
Review generated posts, hashtags, SEO keywords, and emails before publishing. Do not install as-is if you need brand-neutral output, confidential input handling, or strict platform-compliance guidance. If used, remove the hard-coded Yucheng/Mingyang terms, add explicit privacy and outbound-email compliance notices, pin dependencies, and avoid sending sensitive files to the LLM provider without approval.
scripts/hashtag_generator.py:34Unrelated Third-Party Brand Injection into User-Generated Marketing Content
README.md:32Unpinned Runtime Dependency Installation and Missing Declared Requirements File
Advertising cross-platform content, cold email, reporting, and competitor analysis without implementation is a deceptive capability mismatch. In security terms, this undermines informed consent and reviewability because the declared surface area does not correspond to the real operational surface area of the skill.
Advertising cross-platform content, cold email, reporting, and competitor analysis without implementation is a deceptive capability mismatch. In security terms, this undermines informed consent and reviewability because the declared surface area does not correspond to the real operational surface area of the skill.
Advertising cross-platform content, cold email, reporting, and competitor analysis without implementation is a deceptive capability mismatch. In security terms, this undermines informed consent and reviewability because the declared surface area does not correspond to the real operational surface area of the skill.
Advertising cross-platform content, cold email, reporting, and competitor analysis without implementation is a deceptive capability mismatch. In security terms, this undermines informed consent and reviewability because the declared surface area does not correspond to the real operational surface area of the skill.
The file presents headings and submission/promotional copy partly in Chinese and provides no indication that language should be selected based on user preference or regional context. Under the policy, forcing a specific language without opt-in can be a natural-language policy violation unless the locale restriction is justified.
The phrase "Just say: 'Create a marketing strategy for my SaaS product.'" promotes auto-activation on a very common, natural-language request. In agent ecosystems that trigger skills from broad phrases, this can cause unintended invocation of a powerful skill with executable scripts, increasing the chance of unreviewed code paths, unexpected external calls, or inappropriate takeover of unrelated user sessions.
The README advertises creation of '5-stage high-converting cold email sequences' but does not warn users that the skill can generate outbound messaging that may be used for spam, policy violations, or reputational harm. In this context, a marketing automation skill increases the likelihood of misuse because email generation is a core feature rather than an incidental capability.
The README states the skill has built-in LLM integration and instructs users to set an API key, but it does not clearly warn that prompts and business data may be sent to external LLM/API services. For a marketing skill likely to process customer data, competitive intelligence, and internal strategy, this omission creates a meaningful risk of unintended data disclosure or insecure key handling.
The README suggests broad natural-language trigger phrases like 'Generate a marketing strategy' and similar requests, which can cause the skill to activate in situations the user may not intend. In an agent environment, over-broad activation can lead to unnecessary execution of marketing workflows, external API calls, or generation of sensitive outbound content without clear user confirmation.
The skill advertises executable scripts that use environment variables and file I/O, but the manifest does not declare any tool scope or permissions boundaries. This creates an authorization gap where the runtime may grant broader capabilities than users expect, increasing the risk of unintended file access or secret exposure when the skill is invoked.
The trigger phrases are extremely broad and cover many generic marketing terms, making accidental or overbroad invocation more likely. When combined with script execution, file access, and outbound LLM/API use, broad triggering increases the chance that unrelated user data is processed by this skill without clear intent.
The skill states it uses API credentials and LLM-backed scripts, but does not include a clear user-facing warning that prompt content, files, or business data may be transmitted to an external provider. This is especially sensitive in a B2B marketing context, where ICPs, competitor notes, email copy, and reports may contain confidential customer or pipeline information.
The entire skill file is written in Chinese and does not provide any language-selection option, alternative locale, or justification that the content is intended only for a Chinese-speaking or region-specific audience. Under the policy, forcing a specific language without user opt-in is a natural-language locale violation.
The phrase setting output quality to the standard of a "professional white marketing team" embeds a racially framed normative benchmark into the skill. In a content-generation system, this can propagate biased assumptions, produce exclusionary or discriminatory outputs, and normalize race-based quality judgments across customer-facing marketing materials.
The document title and content are presented primarily in Chinese, which can impose a language choice on users if this file is used as required skill guidance. Because the policy only allows fixed language behavior when users are given a choice or the locale constraint is clearly justified, this mandatory Chinese presentation is a natural-language policy concern.
The line says SEO tasks 'must' reference this keyword matrix, while the matrix is written in Chinese and mixes Chinese/English terminology. This creates a mandatory language/locale constraint without offering user opt-in or explaining why that locale is required.
This markdown file consists wholly of Chinese-language instructional content and does not provide any user opt-in, alternative language option, or justification that the skill is intended only for a Chinese-speaking or region-specific audience. Under the policy, forcing a specific language without user choice is a natural-language locale violation.
The document explicitly advises bypassing Xiaohongshu's commercial lead-generation restrictions by disguising contact information with symbols or homophones. This enables policy evasion and can facilitate off-platform solicitation, reducing platform safeguards and increasing legal, trust, and account-enforcement risk; in a marketing-execution skill, that context makes the guidance more operationally dangerous rather than merely descriptive.
The entire skill document is written in Chinese and provides no indication that users may choose another language or locale. Under the policy rule for natural-language violations, forcing a specific language without opt-in is a reportable issue.
This Python file contains user-facing natural-language documentation and output entirely in Chinese, including the tool description and usage examples. Under the policy rule for language/locale, this is a violation because the skill imposes a specific language without documenting user opt-in or offering an alternative locale choice.
This code file contains user-facing natural-language documentation and CLI help context in Chinese only, which can impose a specific language on users without opt-in. The policy allows locale constraints when they are explicitly documented and justified, but no such justification or language selection is provided here.
The file's natural-language descriptions and prompt instructions are written to operate in Chinese and generate Chinese-platform-specific output, but there is no user opt-in or configurable language selection. Under the stated policy, forcing a specific language or locale without choice is a violation unless clearly justified and documented.
The script reads arbitrary source content from a local file and sends up to 3000 characters of it to an external LLM service without any user-facing disclosure, consent flow, redaction, or sensitivity checks. In a marketing skill, source files may contain unpublished campaigns, customer data, internal strategy, or regulated business information, so silent exfiltration to a third-party model provider creates a real confidentiality and compliance risk.
The module docstring, usage guidance, argument help text, and user-facing output are presented only in Chinese. This creates a language/locale restriction in the skill's natural-language interface without user opt-in or justification that the skill is intended only for a Chinese-speaking or region-specific context.
The CLI exposes a quarterly report mode and prints that the quarterly report was generated "based on monthly data aggregation," but the implementation does not aggregate any monthly data at all. It only prints success messages and optionally writes a hardcoded placeholder string, which directly contradicts the inline comments and user-facing output.