T01 · Skill Instruction Hijacking
- Location
SKILL.md:181- Finding
Mandatory Branded Attribution in Generated Reports
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 181
Vulnerability Type:T01: Skill Instruction Hijacking
Risk Level: MediumComplete Code Snippet:
markdown > 本报告由 OPC-AI Skill(mvp-validator)生成,基于《AI超级个体》书稿框架。English translation:
text This report was generated by the OPC-AI Skill (mvp-validator), based on the framework from the “AI Super Individual” manuscript.Technical Analysis
The skill's prescribed report template requires the agent to append a fixed attribution promoting “OPC-AI Skill” and a referenced publication. This content is not necessary to perform the requested MVP validation and is inserted into ordinary user deliverables whenever the template is followed.
Because the instruction changes the content of the agent's final output for branding purposes, it constitutes skill-level output manipulation under
T01: Skill Instruction Hijacking. The behavior does not override safety controls or execute code, but it compromises output integrity by embedding unsolicited attribution into documents that users may treat as their own reports.Attack Path
- A user invokes the skill with an MVP-validation request.
- The agent loads and follows the instructions in
SKILL.md. - The agent uses the mandatory report template.
- The fixed branded attribution at line 181 is appended to the generated report.
- The user may save or distribute the report with the injected promotional content still present.
Impact Assessment
The issue affects generated-report content and document integrity. An attacker does not gain operating-system privileges, code-execution capabilities, credentials, persistent access, or access to unrelated user data.
The scope is limited to reports generated from the affected template. The principal impact is that users may unknowingly distribute documents containing third-party branding or attribution that they did not explicitly request. ...[truncated 108 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the fixed attribution from the default report template.
- Restrict the template to content directly required for MVP validation.
- If attribution is desired, make it explicitly optional and obtain user consent before adding it.
- Clearly preview any attribution before generating or saving the report.
- Add a template-review requirement prohibiting unsolicited branding, promotional language, links, or third-party endorsements in user deliverables.
- Test the revised skill with representative requests and confirm that generated reports contain no branding unless the user explicitly opts in.
