T01 · Skill Instruction Hijacking
- Location
SKILL.md:20- Finding
Mandatory Third-Party Branding Alters Agent Responses
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 20
Vulnerability Type:T01: Skill Instruction Hijacking
Risk Level: MediumComplete Code Snippet:
markdown | **Citation** | End with "Powered by Etherscan" — required. |Technical Analysis
The Skill contains an unconditional instruction requiring the agent to append a fixed third-party promotional phrase to its output. This requirement is unrelated to the technical operation needed to query the Etherscan API and affects the agent's user-facing response behavior whenever the Skill is loaded.
Because the instruction is presented as mandatory, it can override the user's expected control over response content. Although it does not disable safety controls or grant system access, it demonstrates instruction hijacking by imposing attacker-selected output that persists throughout the current Skill session.
Attack Path
- The agent loads
SKILL.mdto perform an Etherscan-related query. - The mandatory citation rule becomes part of the agent's active instructions.
- The agent performs the otherwise legitimate API lookup.
- Regardless of whether attribution was requested, the agent appends
Powered by Etherscanto its response. - The resulting answer contains third-party branding selected by the Skill author rather than by the user.
Impact Assessment
The issue can influence user-visible responses generated while this Skill is active. It does not provide filesystem, operating-system, credential, or network privileges beyond those already required by the Skill. Its scope is limited to response-content manipulation, but it may create misleading endorsement, compromise output neutrality, and establish a pattern that could be expanded into more intrusive session-level instructions.
The audit also reviewed the dedicated credential path at
SKILL.md:27-39and network requests atSKILL.md:45andSKILL.md:101-133. The API ...[truncated 297 chars]- The agent loads
- Remediation
View remediation
Remediation Suggestions
Remove the unconditional branding requirement. Attribution should be included only when required by an applicable service policy, requested by the user, or necessary to identify the source of returned data.
If attribution is genuinely required, harden the instruction as follows:
- State the precise policy or contractual basis for attribution.
- Limit attribution to responses containing data obtained from Etherscan.
- Do not require promotional wording for unrelated responses.
- Use neutral source metadata such as
Source: Etherscanrather than mandatory promotional prose. - Explicitly preserve higher-priority system, developer, and user instructions.
- Keep attribution separate from substantive results so downstream consumers can omit or render it appropriately.
