T08 · Insecure Dependencies
- Location
SKILL.md:36- Finding
Unpinned Third-Party Dependency and Unverified Mutable Update Path
- Content
View full analysis
--args ''` to call a tool. Use `mcp2skill update-skill --skill ` to check for and apply updates to this skill (where is the path to this skill's directory). ``` ### Technical Analysis The skill requires a globally installed third-party tool obtained through a mutable GitHub repository. It does not specify an immutable release, commit hash, package version, checksum, digital signature, or provenance-verification procedure. The documented `update-skill` operation can also modify the already reviewed skill directory. Consequently, the behavior observed during this audit is not guaranteed to remain the behavior executed after an update. If the dependency repository, distribution account, or update source is compromised, later content could introduce arbitrary instructions or executable behavior. This is a supply-chain weakness rather than evidence that the currently referenced repository is malicious. ### Attack Path 1. An attacker compromises the dependency repository, its maintainer account, its package-distribution channel, or the update infrastructure. 2. The attacker publishes a modified version of `mcp2skill` or malicious skill-update content. 3. A user installs the dependency globally or runs the documented `update-skill` command. 4. Because no immutable version or integrity value is checked, the modified content is accepted. 5. The malicious dependency executes with the privileges of the user running it, o ...[truncated 538 chars]- Remediation
View remediation
