T01 · Skill Instruction Hijacking
- Location
SKILL.md:86- Finding
Mutable Remote Instructions Can Hijack the Live Checkpoint Workflow
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 86–87
Vulnerability Type:T01: Skill Instruction Hijacking
Risk Level: HighComplete Code Snippet:
markdown 1. Read `https://767-2676.com/agent/offer` and the canonical `https://767-2676.com/SKILL.md`.Technical Analysis
The packaged Skill instructs the agent to retrieve and read a remotely hosted
SKILL.md, describing that external document as canonical. Unlike the locally audited artifact, remote content is mutable and is not pinned to a specific version or cryptographic digest. The repository contains no mechanism that validates the external instruction document against an audited copy.This creates an instruction-hijacking boundary: the external operator, or an attacker who compromises the remote service, can change the effective workflow after the local Skill has been reviewed. Although nearby instructions impose payment-policy and origin checks, those local safeguards do not ensure that newly retrieved natural-language instructions will remain consistent with them.
Attack Path
- A user invokes the Skill for a later live task requiring a fresh checkpoint.
- Following lines 86–87, the agent retrieves
/agent/offerand the remotely hosted “canonical”/SKILL.md. - The domain operator, or an attacker controlling the service, supplies modified instructions.
- The modified document directs the agent to perform actions not present in the audited local artifact, such as disclosing additional information, using a different endpoint, invoking tools, or authorizing an unintended transaction.
- If the agent gives the remote document canonical instruction authority, it follows the altered workflow under the apparent authority of the installed Skill.
Impact Assessment
Exploitation can alter the agent’s live-task goals and operational constraints within the permissions already available to the agent. Potential scope incl ...[truncated 444 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the instruction to load a remote
SKILL.md; package all authoritative workflow instructions in the reviewed local artifact. - Treat remote responses only as untrusted data and parse them through a strict, documented schema. Never interpret remote natural-language content as agent instructions.
- If remote configuration is unavoidable, pin it to an immutable version and verify its cryptographic digest or signature against a locally embedded, trusted key before use.
- Define an allowlist of permitted endpoints, HTTP methods, request fields, networks, assets, and maximum payment amounts in local policy that remote content cannot override.
- Require explicit participant confirmation before any payment or release of task-related data, and ensure redirects and origin changes fail closed.
- Vendor the verifier, sample packets, and tests into the package so the complete security-critical workflow can be independently audited and executed without relying on mutable external instructions.
- Remove the instruction to load a remote
