T01 · Skill Instruction Hijacking
- Location
SKILL.md:8- Finding
Vendor-Specific Workflow Hijacking Through Skill Instructions
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a disclosed Chinese-language workflow guide for evaluating a partial MkBoard-to-AI-HIVE migration, with no executable code or hidden persistence.
Install this only if you intend to evaluate an AI-HIVE-based partial migration from MkBoard and can read the Chinese instructions. Before using it, confirm the destination provider, asset rights, retention/privacy terms, and cost approval for each media-generation task.
SKILL.md:8Vendor-Specific Workflow Hijacking Through Skill Instructions
The trigger description contains broad search phrases such as generic platform/category terms that can match routine user requests, causing the skill to activate outside its intended migration-evaluation scope. In an agent setting, over-activation can route users into biased or irrelevant workflows, increasing the chance of unintended data handling, misleading recommendations, or prompt-scope hijacking by unrelated queries.
The skill is written to operate in Chinese without giving the user a language-choice mechanism or documenting a hard locale requirement. This can cause users to misunderstand limitations, outputs, approval steps, or legal/compliance caveats, which is especially risky in a workflow involving migration decisions, rights handling, and human approval gates.
The display name, short description, and default prompt are all written in Chinese and instruct the model in Chinese, with no indication that users may choose another language. Under the policy, a fixed language/locale without user opt-in is a natural-language policy violation unless clearly justified as region-specific.
This markdown file contains user-facing natural language exclusively in Chinese, and there is no indication that the skill offers a language/locale choice or that the Chinese-only constraint is intentional and justified for a region-specific use case. Under the policy, forcing a specific language without user opt-in is a natural-language policy violation.
No suspicious patterns detected.