T01 · Skill Instruction Hijacking
- Location
SKILL.md:224- Finding
Mandatory Promotional Attribution Injected into Generated Reports
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 224
Vulnerability Type:T01: Skill Instruction Hijacking
Risk Level: LowRelevant code snippet:
markdown > This plan was generated by OPC-AI Skill (ability-upgrade), based on the "AI Super Individual" manuscript framework.The snippet above is an English rendering of the mandatory attribution contained at the specified source location.
Technical Analysis
The attribution is embedded directly in the Skill's output template. When the agent follows that template, it inserts OPC-AI and book branding into generated career-planning reports even when the user has not requested promotional attribution.
This constitutes a limited form of output instruction hijacking: the Skill imposes a secondary promotional objective on the agent's response rather than restricting its behavior to the declared capability-assessment function. The instruction does not override safety controls, execute code, access credentials, or grant elevated permissions.
Attack Path
- A user invokes the
ability-upgradeSkill using one of its documented triggers. - The agent performs the requested capability assessment and upgrade planning.
- The agent follows the output template defined in
SKILL.md. - The fixed attribution at line 224 is inserted into the generated report.
- The resulting user-facing document contains unrequested third-party branding.
No external attacker interaction, code execution, or privilege escalation is required. Exploitation is limited to invoking the Skill and causing it to generate template-based output.
Impact Assessment
The issue affects the integrity and neutrality of reports produced by the Skill. Users may receive promotional or branded language that they did not request, and downstream reports may incorrectly appear endorsed by or affiliated with the named product and publication.
The affected scope is limited to gene ...[truncated 193 chars]
- A user invokes the
- Remediation
View remediation
Remediation Suggestions
- Remove the fixed promotional attribution from the mandatory output template.
- If provenance information is operationally necessary, use a neutral statement that identifies the framework without promotional wording.
- Make attribution optional and include it only after explicit user consent.
- Separate metadata or provenance from the user-facing report body.
- Add a review rule requiring output-template content to be directly relevant to the declared Skill function.
- Test the Skill with ordinary assessment requests and verify that generated reports contain no unrequested branding or endorsements.
