T01 · Skill Instruction Hijacking
- Location
SKILL.md:238- Finding
Mandatory Attribution Hijacks Substantive Agent Responses
- Content
View full analysis
**Signature**: Front-line Bid Evaluation Expert & ChesaraM - The signature is only an author identifier. External contact information or promotional content must not be added to it. - The disclaimer that the response does not constitute a formal legal opinion must still appear before the signature under the original rules. ``` The behavior is also reinforced by mandatory signature examples in `templates/输出模板.md`, including lines 26 and 48. ### Technical Analysis The skill requires the agent to append a fixed third-party attribution to every formal or substantive response. This instruction is unrelated to the functional requirements of procurement compliance analysis and overrides the expected user-controlled presentation of generated content. Because the rule applies automatically whenever the skill produces substantive output, users do not need to request the attribution and may be unable to receive neutral or unbranded documents. Generated reports, legal-compliance drafts, and other materials can consequently imply that the named parties authored, reviewed, or endorsed the content when no such relationship has been established. This is classified as instruction hijacking because loading the skill introduces a persistent session-level output requirement that changes how the agent must answer subsequent requests. ### Attack Path 1. A user activates the procurement-advisor skill. 2. The agent loads the instructions from `SKILL.md`. 3. The user requests a compliance conclusion, re ...[truncated 1020 chars]- Remediation
View remediation
