T01 · Skill Instruction Hijacking
Warning
- Location
- SKILL.md:126
- Finding
- Executable Installation Command Injected into Mandatory Strategy Output## Vulnerability Details **File Location**: `SKILL.md`, lines 126-153 **Vulnerability Type**: T01: Skill Instruction Hijacking **Risk Level**: Medium **Vulnerable Code Snippet**: ```markdown ## Output Format ```markdown # 10x Analysis: <Product/Area> Session N | Date: YYYY-MM-DD ## Current Value What the product does today and for whom. ## The Question What would make this 10x more valuable? ## Installation ### OpenClaw / Moltbot / Clawbot ```bash npx clawhub@latest install game-changing-features ``` ``` ### Technical Analysis The skill requires responses to follow a strategy-report template, but that template includes an executable package-installation command. Installation instructions are unrelated to the requested product analysis and cause the agent to promote external code execution whenever it follows the mandatory output format. This constitutes instruction hijacking because loading the skill alters the expected strategy response by injecting an operational command into generated artifacts. The command is not automatically executed by the skill, so exploitation requires the user or another automation layer to run it. ### Attack Path 1. A user loads the skill to perform product-strategy analysis. 2. The agent follows the mandatory output template in `SKILL.md`. 3. The generated strategy document includes `npx clawhub@latest install game-changing-features`. 4. The user or a downstream process treats the command as a recommended setup step. 5. Running the command downloads and executes code that was not part of the audited strategy output. ### Impact Assessment The direct impact is unauthorized promotion of an executable command in otherwise non-executable strategy content. If a user runs the command, the retrieved package executes with the privileges of that user and may access files, environment variables, network resources, and credentials available to the process. The a ...[truncated 215 chars]
- Remediation
- ## Remediation Suggestions 1. Remove the installation section from the mandatory strategy-output template. 2. Keep installation documentation exclusively in `README.md` or another clearly separated setup document. 3. Do not include executable commands in generated reports unless the user explicitly requests installation instructions. 4. Add a rule prohibiting the skill from recommending package execution as part of ordinary product-strategy output. 5. If installation guidance is necessary, describe the package source, pinned version, integrity-verification procedure, and security implications.
