T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:289
- Finding
- Unpinned Third-Party Skill Installation Creates Supply-Chain Risk<![CDATA[ ## Vulnerability Details **File Location**: `SKILL.md`, lines 289-305 **Vulnerability Type**: Unpinned and mutable third-party dependencies **Risk Level**: Medium ### Vulnerable Code ```markdown If those setup skills are not installed beside this product skill, use the downloads below. Core AgentPMT setup skills: - What AgentPMT is: ../what-is-agentpmt - ClawHub page: https://clawhub.ai/agentpmt/what-is-agentpmt - OpenClaw install: `openclaw skills install what-is-agentpmt` - skills.sh install: `npx skills add AgentPMT/agent-skills --skill what-is-agentpmt` - AgentPMT account MCP/REST setup: ../agentpmt-account-mcp-rest-api-setup - ClawHub page: https://clawhub.ai/agentpmt/agentpmt-account-mcp-rest-api-setup - OpenClaw install: `openclaw skills install agentpmt-account-mcp-rest-api-setup` - skills.sh install: `npx skills add AgentPMT/agent-skills --skill agentpmt-account-mcp-rest-api-setup` skills.sh install script: ```bash npx skills add AgentPMT/agent-skills --skill what-is-agentpmt npx skills add AgentPMT/agent-skills --skill agentpmt-account-mcp-rest-api-setup ``` ``` ### Technical Analysis The documented setup process invokes `npx` and installs skills from mutable external sources without specifying an immutable package version, repository commit, checksum, or signature. Consequently, the content installed when a user follows these instructions may differ from the content available when this Skill was audited. Because the referenced setup skill handles account and API connection details, a compromised dependency could provide malicious credential-handling instructions or introduce unsafe executable behavior. The project does not instruct users to inspect or verify the downloaded content before activating it. This is a supply-chain weakness rather than evidence that the currently referenced dependencies are malicious. ### Attack Path 1. An attacker compromises the upstream package, repository, publishing account, distribution ...[truncated 1210 chars]
- Remediation
- <![CDATA[ ## Remediation Suggestions 1. Pin every dependency to an immutable package version and repository commit. 2. Publish cryptographic checksums or signed release manifests and verify them before installation. 3. Avoid floating repository references and implicit latest-version resolution. 4. Use a trusted registry with package provenance and signature verification enabled. 5. Require the downloaded skill content to be reviewed before it is activated. 6. Run installation in a restricted environment with minimal filesystem, network, and credential access. 7. Document the expected dependency hashes and provide a process for securely updating them. 8. Prefer locally bundled, audited setup documentation when feasible. ]]>
