T01 · Skill Instruction Hijacking
- Location
SKILL.md:15- Finding
External Runtime Rules Can Hijack Skill Instructions
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 15–18
Vulnerability Type: External instruction redirection with priority override
Risk Level: HighVulnerable Code
markdown ⚠️ STOP — You MUST read and strictly follow the shared runtime rules before proceeding. Do NOT select or call any tool until all rules are read. These rules have the highest priority. → Read `../gate-runtime-rules.md` → Also read `../info-news-runtime-rules.md` for gate-info / gate-news shared rules (tool degradation, report standards, security, routing, and optional local maintenance when `scripts/` is present).Technical Analysis
The skill mandates loading two instruction files from its parent directory and explicitly declares those external instructions to have the “highest priority.” Neither referenced file is included in the audited artifact, so its contents, integrity, and security properties cannot be verified.
Because the paths escape the project root through
../, the skill’s effective behavior depends on mutable files outside the reviewed package. Any party able to create or modify either parent-directory file could introduce instructions that alter tool selection, routing, data handling, maintenance operations, safety constraints, or report output without changing the audited skill itself.This constitutes instruction hijacking because loading the skill establishes an unaudited external control channel for changing the Agent’s current-session behavior. The external rules cannot legitimately override system or developer instructions, but the skill text nevertheless attempts to assign them maximum priority within its workflow.
Attack Path
- An attacker obtains write access to the directory containing
gate-runtime-rules.mdorinfo-news-runtime-rules.md, or influences how those files are provisioned. - The attacker inserts malicious Agent instructions into one of those files.
- A user invokes this skill.
- Before selecting or ca ...[truncated 1040 chars]
- An attacker obtains write access to the directory containing
- Remediation
View remediation
Remediation Suggestions
- Bundle every required runtime-rule document inside the audited skill package.
- Replace parent-directory references with package-relative paths that cannot escape the project root, such as
references/gate-runtime-rules.md. - Remove language assigning externally loaded content “highest priority.”
- Explicitly state that skill and referenced instructions cannot override system, developer, platform-security, or user-consent requirements.
- Include all referenced rule files in release review, integrity verification, and version control.
- If shared rules must remain external, verify them against a pinned cryptographic digest and fail closed when verification fails.
- Restrict external rules to declarative configuration with a documented schema rather than unrestricted natural-language instructions.
- Ensure external configuration cannot expand the skill’s tool allowlist, request additional privileges, initiate maintenance actions, or change data-disclosure policy.
- Add packaging tests that reject references resolving outside the skill root.
