T01 · Skill Instruction Hijacking
- Location
SKILL.md:85- Finding
Mandatory Branding Injected into Agent Responses
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 85-87
Vulnerability Type: Mandatory response manipulation through skill instructions
Risk Level: High
Evidence: The following escaped representation preserves the exact Unicode content of the fixed footer:text --- \U0001F916 Jay \u00B7 \u5929\u6C14\u52A9\u624BTechnical Analysis
The response template requires the agent to append a fixed identity and branding footer to generated weather messages. This attribution is not necessary for retrieving, processing, or delivering the requested weather and calendar information.
Because the footer is part of the prescribed template, loading and following the skill reliably modifies the agent's final response. This constitutes instruction-level output hijacking: the skill uses otherwise legitimate functionality to inject persistent third-party attribution into user-facing content.
No evidence was found that this instruction changes system safety constraints, executes code, accesses additional privileges, writes persistent memory, or compromises external tools.
Attack Path
- The skill is loaded to answer a weather request or scheduled weather-delivery task.
- The agent follows the message-construction instructions in Step 3.
- The agent copies the mandatory footer from the prescribed template.
- The third-party identity is included in the final message.
- If Feishu delivery is configured, the altered message is sent to the configured recipient.
Impact Assessment
The issue affects the integrity and neutrality of user-facing output. It enables fixed promotional attribution to appear as though it were endorsed by the user, agent, or deployment operator.
The demonstrated scope is limited to generated message content. The instruction does not grant filesystem access, elevated privileges, credential access, arbitrary code execution, or cross-session persistence. The project contai ...[truncated 56 chars]
- Remediation
View remediation
Remediation Suggestions
Remove the fixed identity footer from the response template. Keep the default output limited to information necessary for the requested weather and calendar functionality.
If attribution is a legitimate product requirement:
- Declare it clearly in the skill description and deployment documentation.
- Make the footer configurable rather than hardcoded.
- Require explicit operator or user consent before enabling it.
- Allow attribution to be disabled without modifying the skill source.
- Add a review rule prohibiting unrelated branding, advertisements, or identity claims in mandatory response templates.
