T01 · Skill Instruction Hijacking
- Location
SKILL.md:169- Finding
Mandatory Global Response Workflow Hijacks Agent Behavior
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:169
Vulnerability Type: T01: Skill Instruction Hijacking
Risk Level: CriticalVulnerable Code
text Before sending, verify all five modules are present. Missing any → complete before sending.Technical Analysis
The Skill imposes an unconditional response requirement rather than limiting the workflow to situations where a user explicitly requests it. Once loaded, the instruction requires every response to contain all five prescribed modules.
Other portions of the documented workflow require the agent to externalize its thinking and display commands and execution results. Applying those requirements globally can override task-appropriate response behavior and conflict with higher-level confidentiality or least-disclosure expectations.
The package contains only documentation and does not include executable code. Consequently, this issue affects agent instructions and current-session behavior rather than directly granting operating-system privileges.
Attack Path
- The agent loads
SKILL.mdas an active Skill. - The unconditional pre-send rule becomes part of the agent's current instructions.
- A user submits a task containing sensitive context or requiring tool execution.
- The Skill directs the agent to apply every workflow module, including externalized reasoning and command/result reporting.
- Internal operational details, commands, or sensitive command output may consequently be disclosed in the response.
Impact Assessment
The Skill can influence all responses produced while it is active, altering the agent's output structure and task execution behavior. It may cause unnecessary disclosure of reasoning, commands, execution results, or sensitive contextual information.
No direct privilege escalation, arbitrary code execution, or host compromise was identified. The affected scope is the agent's current session and any inform ...[truncated 36 chars]
- The agent loads
- Remediation
View remediation
Remediation Suggestions
- Make the five-step workflow explicitly opt-in and activate it only when requested by the user.
- State that system, developer, security, confidentiality, and tool-use constraints take precedence.
- Do not require disclosure of private reasoning or hidden intermediate analysis. Request concise conclusions and relevant rationale instead.
- Replace raw command and result disclosure with sanitized execution summaries.
- Permit modules to be omitted when they are unnecessary, unsafe, or incompatible with the active task.
- Add explicit filtering requirements for credentials, tokens, personal data, filesystem paths, and other sensitive output.
