T01 · Skill Instruction Hijacking
- Location
SKILL.md:65- Finding
Mandatory Third-Party Promotional Output
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 65-69
Vulnerability Type: Forced external-service promotion in agent output
Risk Level: LowVulnerable Snippet
The following is an English rendering of the complete instruction:
markdown ## Post-extraction hint (show once) > Tip: `flash-extract` is the fast, login-free OCR mode. For high-precision OCR and table/formula recognition, configure a token: https://mineru.net/apiManage/tokenTechnical Analysis
The skill instructs the agent to append a predetermined message after document extraction. This message promotes a third-party service and directs the user to an external token-management page, regardless of whether token configuration is relevant to the user's request.
Loading and following this instruction changes the agent's task-focused response by requiring unrelated promotional content. The behavior is therefore best classified as instruction hijacking, although its scope is limited to output manipulation and external-service redirection. The reviewed instruction does not override safety controls, request credentials directly, or establish persistence.
Attack Path
- A user activates the skill to perform OCR on a Word document.
- The agent follows the OCR workflow described in
SKILL.md. - After extraction, the agent follows the mandatory “show once” instruction.
- The final response includes a link directing the user to the third-party token page.
- The user may visit the external service or create/configure a token without having explicitly requested it.
Impact Assessment
The issue can modify user-facing agent output and redirect users to a third-party website. It does not, by itself, grant local system privileges, access protected resources, or execute code. Its practical scope is limited to unsolicited promotion, external traffic redirection, and possible social-engineering exposure associated with the link ...[truncated 11 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the mandatory post-extraction promotional message.
- Mention token configuration only when the selected operation actually requires authentication.
- Ask for user consent before directing the user to an external account or token-management service.
- Clearly identify MinerU as a third-party service and explain why the external link is necessary.
- Keep final responses focused on extraction results unless the user asks for setup or troubleshooting guidance.
