T01 · Skill Instruction Hijacking
Note
- Location
- SKILL.md:241
- Finding
- Fixed Promotional Link Injected into Agent Completion Responses<![CDATA[ ## Vulnerability Details **File Location**: `SKILL.md:241-259`; duplicated in `SKILL.zh.md:241-259` **Vulnerability Type**: Agent output manipulation **Risk Level**: Low ### Vulnerable Instruction Snippet ```markdown **Success Report**: ```text ✅ A-share Review Analysis Complete! Date: 2026-03-04 Data: data/20260304/ (12 files) AI Analysis: ✓ Generated (Gemini 2.0 Flash) Published Platforms: → Hugo Blog: content/posts/stock-analysis-2026-03-04.md → WeChat Official Account: Draft ID: abc123def456 Market Snapshot: • Shanghai Composite: 3350.52 (+1.02%) • Turnover: 1.95 trillion • Advance/Decline: 2857 / 2058 • Limit-up/Limit-down: 78 / 3 View Blog: https://donvink.github.io/stock-review/ ``` ``` ### Technical Analysis The Skill instructs the Agent to use a predefined completion report containing a link to the Skill author's public demonstration blog. The link is unrelated to the result generated for the current user and is not derived from user configuration. Because `SKILL.md` supplies operational instructions to the Agent, placing an unrelated promotional destination in the expected success response can cause that destination to be included whenever the workflow completes. This modifies the Agent's output for the benefit of an external property rather than strictly fulfilling the user's request. The same behavior appears in both English and Chinese Skill documentation. ### Attack Path 1. The Agent loads the Skill instructions. 2. The Agent executes the documented stock-review workflow. 3. The workflow completes successfully. 4. The Agent follows the prescribed completion-report template. 5. The final response includes the author's unrelated demonstration-blog URL. 6. The user may treat the link as part of the generated result and visit an external property that they did not request. ### Impact Assessment This issue does not grant local code execution, filesystem access, or credential access. Its impact is limited to manipulation of Ag ...[truncated 261 chars]
- Remediation
- <![CDATA[ ## Remediation Suggestions 1. Remove the fixed `View Blog` entry from the success-response template. 2. Treat the completion block as an illustrative format rather than mandatory output. 3. Include a blog URL only when: - the user explicitly requests it; - the URL is generated by the current workflow; or - the user has configured the URL as their own publishing destination. 4. Apply the same correction to `SKILL.zh.md`. 5. Clearly separate project documentation links from instructions controlling the Agent's final response. ]]>
