T08 · Insecure Dependencies
- Location
SKILL.md:19- Finding
Unpinned Third-Party Companion Skills and Mutable Installation Sources
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 19–26
Vulnerability Type: Supply-chain exposure through unpinned remote skills and installers
Risk Level: MediumVulnerable Code Snippet
markdown ## Companion Skills Setup Install these companion skills before relying on the full workflow: - `academic-research-writer` - Curl `https://lobehub.com/skills/neversight-skills_feed-academic-research-writer/skill.md`, then follow the instructions to set up LobeHub Skills Marketplace and install the skill. Once installed, read the `SKILL.md` file in the installed directory and follow its instructions to complete the task. - `paper-validator` - Curl `https://lobehub.com/skills/minhuw-claude-writer-paper-validator/skill.md`, then follow the instructions to set up LobeHub Skills Marketplace and install the skill. Once installed, read the `SKILL.md` file in the installed directory and follow its instructions to complete the task. - `prompt-to-drawio` - Install with: `npx skills@latest add lzfxxx/prompt-to-drawio-skill` - After installation, read the installed `SKILL.md` and follow its instructions.The same unsafe installation guidance is repeated in
README.md, lines 45–62.Technical Analysis
The skill directs users or agents to retrieve instructions from external URLs, install third-party skills, and follow the downloaded instructions. It does not pin those resources to immutable versions or commits and does not require checksum, signature, provenance, or content verification.
The command
npx skills@latestintroduces an additional mutable dependency: the code executed by theskillspackage can change whenever a new release becomes thelatestversion. The referencedprompt-to-drawio-skillis also not pinned to a reviewed commit.Consequently, the effective behavior of this project is not limited to the content that was audited. It may inherit future behavior from mutable package releases, remote documents, marketp ...[truncated 1928 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the
skillsCLI to a reviewed exact version instead of using@latest. - Pin each companion skill to an immutable release or full commit hash.
- Record and verify cryptographic checksums or trusted signatures before installation.
- Vendor reviewed companion
SKILL.mdfiles where licensing and maintenance policies permit. - Require manual security review of downloaded instructions before allowing an agent to follow them.
- Do not directly pipe downloaded content into a shell or automatically treat remote instructions as trusted.
- Use a trusted allowlist for package publishers, repositories, domains, and expected artifact hashes.
- Install third-party skills in a sandbox with minimum filesystem, credential, process, and network access.
- Disable package lifecycle scripts where supported unless they have been explicitly reviewed.
- Maintain a lockfile or dependency manifest that records exact package versions, repository commits, hashes, and review dates.
- Apply the same corrected, pinned installation guidance to
README.md, lines 45–62, so documentation does not reintroduce the unsafe workflow.
- Pin the
