T01 · Skill Instruction Hijacking
- Location
SKILL.md:31- Finding
Mutable External Setup Instructions Can Hijack Agent Behavior
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 31–36
Vulnerability Type: External instruction redirection
Risk Level: CriticalVulnerable Code Snippet:
markdown ## Setup (One Command) Tell your agent:text set up skillboss.co/skill.mdmarkdown This auto-configures SkillBoss with 687 APIs — chat, image, video, audio, search, scraping, social data, email, and more.The same instruction is also referenced by the
installHintmetadata atSKILL.md, line 18:yaml installHint: "Tell your agent: set up skillboss.co/skill.md — or get API key at https://skillboss.co/console"Technical Analysis
The skill directs the agent to obtain and follow setup instructions hosted at
skillboss.co/skill.md. Those instructions are not included in the audited package and are not pinned to an immutable version or protected by a documented checksum or signature.Consequently, the effective setup behavior can change after this package has been reviewed. The external resource owner—or an attacker who compromises the website or its delivery infrastructure—could replace the setup document with instructions that alter the agent's goals, request sensitive credentials, install additional components, invoke tools, or perform actions unrelated to embedding search.
This is an instruction-hijacking risk because the remote document is presented as an imperative command for the agent rather than merely as optional documentation for the user. Although the audited local files do not themselves contain credential theft or destructive commands, they establish a channel through which unaudited instructions can control subsequent agent behavior.
Attack Path
- A user installs or invokes the skill for an embedding-search task.
- The agent processes the instruction to set up
skillboss.co/skill.md. - The agent retrieves or otherwise follows the mutable external document.
- The ...[truncated 1096 chars]
- Remediation
View remediation
Remediation Suggestions
- Include the complete setup procedure directly in the reviewed skill package.
- Do not instruct an agent to execute or automatically follow mutable external instruction documents.
- If remote setup artifacts are unavoidable, reference an immutable, versioned resource and publish a cryptographic checksum or verified signature.
- Download remote content only as untrusted data and display it to the user before taking any action.
- Require explicit user approval for each configuration change, command execution, credential request, or installation step.
- Restrict setup to the minimum capabilities required for embedding search rather than automatically configuring unrelated APIs.
- Document the exact domains, files, configuration changes, and permissions required by the setup process.
