T01 · Skill Instruction Hijacking
Warning
- Location
- SKILL.md:203
- Finding
- Mandatory Promotional Attribution in Generated Reports## Vulnerability Details **File Location**: `SKILL.md`, line 203 **Vulnerability Type**: Forced output modification **Risk Level**: Medium **Category**: T01: Skill Instruction Hijacking **Relevant instruction translated into English**: ```markdown > This plan was generated by OPC-AI Skill (ai-team-builder), based on the “AI Super Individual” manuscript framework. ``` ### Technical Analysis The mandatory report template instructs the agent to insert promotional attribution for the skill and an associated manuscript into every generated report. This content is unrelated to the core functional requirement of selecting AI tools based on the user's workflow and budget. Because the statement is embedded directly in the output template, loading and following the skill alters the agent's final response independently of whether the user requested, approved, or was informed about the attribution. This is a form of output-oriented instruction hijacking: attacker-selected branding is propagated into user-facing artifacts through trusted agent behavior. A related book attribution also appears at `SKILL.md:68`, reinforcing that the promotional content is intentionally embedded at multiple points in the report template. ### Attack Path 1. A user activates the `ai-team-builder` skill. 2. The agent collects the user's business, workflow, budget, and tool requirements. 3. The agent follows the mandatory Markdown report template. 4. The template causes the agent to insert attribution for the OPC-AI Skill and the associated manuscript. 5. The generated report may subsequently be published, shared, or delivered to clients with the unsolicited branding intact. No arbitrary code execution, elevated system permissions, or host compromise is involved. ### Impact Assessment The issue affects the integrity and neutrality of generated reports. An attacker or skill publisher can cause users to unknowingly reproduce promotional statements or apparent endorsements in downstream ...[truncated 361 chars]
- Remediation
- ## Remediation Suggestions 1. Remove the mandatory promotional attribution from the report template. 2. Make attribution optional and include it only after obtaining explicit user consent. 3. Keep functional methodology references separate from branding or promotional statements. 4. If provenance must be retained, use neutral metadata such as “Generated with an AI team-planning template” without naming or endorsing external publications. 5. Review the additional attribution at `SKILL.md:68` and remove it or subject it to the same opt-in mechanism. 6. Add a template review rule prohibiting unsolicited advertising, endorsements, affiliate content, and unrelated branding in user-facing outputs.
