T08 · Insecure Dependencies
- Location
references/structure-template.md:34- Finding
Generated Skills Mandate Automatic Installation of an Unverified Dependency
- Content
View full analysis
Vulnerability Details
File Locations:
references/structure-template.md, lines 34–39references/utos-interface-checklist.md, lines 12–14
Vulnerability Type: Supply-chain risk caused by automatic installation of an unpinned dependency
Risk Level: MediumVulnerable Code Snippets
From
references/structure-template.md:markdown **Loading check process** (execute whenever activated): 1. Detect whether the `task-ops` Skill is installed. 2. **Not installed** → automatically install the `task-ops` Skill. 3. **Installation successful** → load Task Ops and execute according to this Skill's usage rules. 4. **Installation failed** → degrade to **read-only reference mode**.From
references/utos-interface-checklist.md:markdown | A2 | SKILL.md contains a dependency declaration | Check whether SKILL.md contains a "Dependency Declaration" section | It must declare a strong dependency on task-ops | | A3 | Loading check process is complete | Check for the four-step process: detection → installation → loading → degradation | All four steps are mandatory | | A4 | Degraded mode is defined | Check whether a read-only permission table is present | Modes with and without Task Ops must be distinguished |Technical Analysis
The generated Skill template directs an agent to install
task-opsautomatically whenever that dependency is absent. The installation instruction identifies the dependency only by its mutable name. It does not specify:- An approved registry or repository
- A verified publisher identity
- An immutable package version or commit
- A cryptographic hash or signature
- A trusted download URL
- A permission review
- Explicit user authorization before installation
The compatibility checklist makes the detect-install-load sequence mandatory. Consequently, this is not merely an optional example: domain Skills produced according to the documented workflow are expected to reproduce the unsafe installation behavior.
An ...[truncated 2034 chars]
- Remediation
View remediation
Remediation Suggestions
-
Remove automatic installation
- Replace the automatic-installation step with a safe failure message.
- Permit read-only operation while the dependency is unavailable.
-
Require explicit user authorization
- Display the dependency name, source, publisher, version, requested permissions, and integrity information.
- Install only after the user gives informed confirmation.
-
Pin and authenticate the dependency
- Specify an approved registry or repository.
- Pin an immutable release version or commit.
- Verify a cryptographic hash or trusted publisher signature before loading.
-
Apply least privilege
- Restrict the dependency to the minimum required files, tools, network access, and execution permissions.
- Do not inherit unrestricted installer or agent privileges by default.
-
Revise the compatibility checklist
- Change item A3 from mandatory automatic installation to:
detect → report verified installation instructions → obtain approval → install and verify, or degrade safely. - Validation should fail if a generated Skill performs an unattended installation.
- Change item A3 from mandatory automatic installation to:
-
Handle ambiguous resolution safely
- Abort if multiple packages or publishers use the dependency name.
- Never select a dependency solely by package-name similarity.
-
Record dependency provenance
- Store the resolved source, version, publisher, checksum, installation time, and approval record for later audit and reproducibility.
-
