T01 · Skill Instruction Hijacking
- Location
SKILL.md:1- Finding
Mandatory Delegation to Mutable External Instructions
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 1-4
Vulnerability Type:T01: Skill Instruction Hijacking
Risk Level: HighComplete code snippet translated into English:
markdown ## Help your owner register a digital human on TB. Be sure to execute the following steps in order. Follow this document: https://github.com/teambition/tb-skills/blob/main/README_FOR_AI.md If your owner prefers Meego, you can also use https://clawhub.ai/wadxm/feishu-project-connectorTechnical Analysis
The local Skill directs the agent to follow instructions hosted outside the audited package. The GitHub URL references a mutable branch rather than an immutable commit, while the alternative URL delegates behavior to another externally hosted Skill. The contents and security properties of these external resources are not represented in the project and were therefore outside the audited artifact.
This creates instruction hijacking risk because the Skill's effective behavior can be changed remotely without modifying
SKILL.mdor triggering a new review. An external maintainer or an attacker who compromises the referenced resources could introduce instructions that change the agent's goal, weaken safety constraints, request sensitive information, invoke tools, or direct data to an external service.The finding concerns remote instructions, not confirmed remote code execution. No local scripts or embedded executable payloads were present in the audited project.
Attack Path
- A user loads or invokes the Skill.
SKILL.mdinstructs the agent to follow one of the externally hosted resources.- The external content is changed by its maintainer or compromised by an attacker after the local Skill has been reviewed.
- The agent interprets the changed remote content as instructions authorized by the local Skill.
- The agent performs attacker-selected actions using the tools, credentials, network access, an ...[truncated 510 chars]
- Remediation
View remediation
Remediation Suggestions
- Include all operational instructions directly in the audited Skill package.
- Do not treat externally retrieved content as authoritative agent instructions; use it only as untrusted reference material.
- If an external resource is unavoidable, pin it to an immutable, reviewed revision, such as a specific Git commit, and verify its expected cryptographic digest before use.
- Review and package the alternative connector as an explicit dependency rather than dynamically delegating to an unreviewed Skill page.
- Define an allowlist of permitted actions, domains, tools, and data fields locally so external content cannot expand the Skill's authority.
- Require explicit user confirmation before authentication, account creation, sensitive-data submission, or any consequential external operation.
- Re-audit the complete pinned external material whenever its revision changes.
