T08 · Insecure Dependencies
- Location
SKILL.md:154- Finding
Unpinned Third-Party Skill Installation Commands
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 154–175
Vulnerability Type:T08: Insecure Dependencies
Risk Level: MediumVulnerable Code
bash ## Related Skills ```bash # Full platform skill (all 150+ apps) npx skills add inference-sh/skills@infsh-cli # Pruna P-Video (fast & economical) npx skills add inference-sh/skills@p-video # Google Veo specific npx skills add inference-sh/skills@google-veo # AI avatars & lipsync npx skills add inference-sh/skills@ai-avatar-video # Text-to-speech (for video narration) npx skills add inference-sh/skills@text-to-speech # Image generation (for image-to-video) npx skills add inference-sh/skills@ai-image-generation # Twitter (post videos) npx skills add inference-sh/skills@twitter-automationTechnical Analysis
The documentation recommends installing multiple third-party skills through
npxwithout pinning them to reviewed package versions or immutable source commits. Consequently, the content installed when a user executes these commands can differ from the content available when this skill was audited.This creates a supply-chain trust boundary: compromise of the package resolution path, the upstream repository or publisher account, or a later malicious upstream change could cause users to install attacker-controlled skill instructions or executable components. The artifact does not itself contain a malicious payload, and exploitation depends on a user or agent executing one of the documented installation commands.
A related concern appears at
SKILL.md:15, where installation instructions are linked from a mutablemainbranch. That link is not directly executed by the skill, but its contents can change after review and could later recommend unsafe commands.Attack Path
- An attacker compromises an upstream skill source, publisher account, repository, or relevant package-resolution channel.
- The attacker modifies one of the unpinned skills or its installation beha ...[truncated 1010 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin every recommended dependency to a reviewed, immutable version or commit rather than a mutable name or branch.
- Prefer commands that resolve exact package versions, release tags backed by immutable artifacts, or full commit hashes.
- Publish and verify cryptographic checksums or signed provenance for downloaded and installed artifacts.
- Replace the mutable
main-branch installation link atSKILL.md:15with a versioned document or immutable commit URL. - Review each related skill's source, installation hooks, transitive dependencies, and requested tool permissions before recommending it.
- Use lockfiles or an equivalent integrity mechanism where the installer supports them.
- Run third-party installation and generation tooling under least privilege, with restricted filesystem, credential, and network access.
- Clearly warn users that the listed commands retrieve third-party content and require independent trust verification before execution.
