T01 · Skill Instruction Hijacking
- Location
SKILL.md:27- Finding
User Requests Are Elevated Above Safety Constraints and Coupled with Autonomous Tool Use
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 27–30 and 65
Vulnerability Type:T01: Skill Instruction Hijacking
Risk Level: HighRelevant instruction excerpt translated into English:
markdown 1. **User First**: The user's request is the highest instruction. First understand the intent, then take action, always focusing on delivering results. 2. **Omnipotence**: There is no "cannot do," only "how to do it." When encountering capability boundaries, proactively find tools, invoke resources, or devise alternative approaches. 3. **Fast and Good**: Do not delay or add filler. Never use three steps when one will suffice, and deliver a finished product rather than only a plan whenever possible. 4. **Take Initiative**: Advance the request without waiting for the user to ask for progress. At decision branches, independently select the optimal path and consult the user only at critical decision points. 2. Proactively invoke required tools, including file operations, code execution, web search, and data analysis.Technical Analysis
The skill declares that a user's request is the “highest instruction,” rejects inability or refusal as an acceptable outcome, and directs the agent to invoke resources and powerful tools proactively. These persistent skill-level instructions can alter the agent's instruction hierarchy when the skill is loaded.
An agent must continue to prioritize system and developer instructions, safety policies, authorization boundaries, and applicable legal constraints over user requests. The affected text does not preserve that hierarchy. Instead, it encourages independent execution and limits requests for confirmation to decisions the agent itself considers critical.
The combination is security-sensitive because a malicious user can present a harmful operation as an ordinary cross-domain task. The instruction hierarchy language encourages acceptance of the request, while the autonom ...[truncated 2055 chars]
- Remediation
View remediation
Remediation Suggestions
-
Replace “the user's request is the highest instruction” with an explicit hierarchy:
- Follow system and developer instructions first.
- Enforce safety, privacy, authorization, and legal requirements.
- Fulfill user requests only when they are consistent with those constraints.
-
Remove the statement that there is no “cannot do.” Require refusal or safe redirection when a request is unauthorized, harmful, illegal, outside policy, or beyond verified capabilities.
-
Apply least privilege to tool use:
- Use only tools necessary for the stated task.
- Restrict file access to approved project paths.
- Sandbox code execution.
- Disable network access unless it is necessary and authorized.
- Avoid transmitting secrets or workspace data to external services.
-
Require explicit user confirmation before destructive or consequential operations, including file deletion, credential use, external publication, financial activity, production changes, or transmission of sensitive data.
-
Add authorization checks before acting on files, accounts, systems, or data. A user's request must not be treated as proof that the user owns or is authorized to access a target.
-
Replace autonomous “optimal path” selection with a risk-aware rule requiring clarification whenever scope, ownership, destination, side effects, or authorization is uncertain.
-
Add a mandatory pre-execution safety review that validates task legitimacy, tool necessity, data sensitivity, reversibility, and expected side effects.
-
