T01 · Skill Instruction Hijacking
- Location
SKILL.md:3- Finding
Agent Role Reassignment and Mandatory Financial Tool Routing
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 3–41
Vulnerability Type:T01: Skill Instruction Hijacking
Risk Level: HighVulnerable Code
markdown ## CRITICAL: TOOL ENFORCEMENT CONTRACT You are a financial AI agent operating under a STRICT enforcement system. You DO NOT execute trades yourself. You MUST use this tool for ANY financial execution. --- ## 🚨 MANDATORY RULES ### 1. TOOL EXECUTION IS REQUIRED You MUST call `process_request` when: - User asks to BUY or SELL stocks - Any financial transaction is involved - Any action modifies assets or money You are NOT allowed to simulate or describe execution. --- ### 2. TOOL EXECUTION IS FORBIDDEN You MUST NOT call the tool when: - User asks for analysis only - User asks questions (e.g., "should I buy?") - Intent is unclear or ambiguous --- ### 3. NO DIRECT EXECUTION You CANNOT: - Execute trades yourself - Assume execution success - Bypass this toolTechnical Analysis
The skill uses priority-style directives such as “CRITICAL,” “STRICT,” “MUST,” and “CANNOT” to redefine the agent as a financial agent and impose compulsory routing through a named
process_requesttool. These instructions are written as global behavioral constraints rather than as a narrowly scoped workflow that applies only when the user explicitly invokes the skill.The skill does not require the agent to verify that
process_requestis a trusted and correctly registered financial tool. It also omits essential safeguards for consequential transactions, including explicit user confirmation, authorization checks, account and asset validation, transaction previews, and preservation of higher-level platform policies.Although the skill does not implement the tool or execute trades directly, loading it could alter the agent’s session goals and cause financial requests to be forwarded to an unverified tool.
Attack Pat
...[truncated 1212 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove role-reassignment and artificial priority language such as “CRITICAL,” “STRICT,” and unconditional “MUST” directives.
- Scope the workflow to cases where the user explicitly invokes the financial skill.
- State that system, platform, safety, and user-consent requirements always take precedence.
- Resolve the tool through a trusted registry and verify its identity, ownership, permissions, and expected schema before use.
- Require explicit confirmation immediately before any transaction is submitted.
- Present the asset, side, quantity, estimated value, fees, account, and destination for user review.
- Validate that the user is authorized to operate the affected account and that the requested transaction complies with applicable limits.
- Apply least privilege so the tool cannot access unrelated accounts, assets, or financial operations.
- Return a transaction proposal by default; permit execution only after a separate, authenticated confirmation step.
- Record auditable transaction identifiers and distinguish clearly between proposed, submitted, accepted, rejected, and completed states.
