T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:192
- Finding
- Unpinned Third-Party Skill Installation Creates a Supply-Chain Risk## Vulnerability Details **File Location**: `SKILL.md:106`, `SKILL.md:192-202`, and `SKILL.md:263-264` **Vulnerability Type**: Unpinned and mutable third-party dependencies **Risk Level**: Medium The Skill recommends installing additional components from a remote repository using `npx`, without pinning the package version, repository commit, or integrity digest. ```markdown - File Management: ../file-management (ClawHub: `file-management`, page: https://clawhub.ai/agentpmt/file-management; skills.sh: `npx skills add AgentPMT/agent-skills --skill file-management`) ``` ```markdown 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 `npx skills add` commands resolve and execute remotely distributed tooling and retrieve content from the mutable `AgentPMT/agent-skills` source. Neither an immutable repository commit nor a cryptographic integrity value is specified. Consequently, the effective dependency content installed by a user can differ from the content that existed when this Skill was audited. This is particularly sensitive for the account MCP/REST setup Skill because that component is expected to provide instructions related to ...[truncated 1594 chars]
- Remediation
- ## Remediation Suggestions 1. Pin every installed dependency to an immutable package version and repository commit. 2. Publish and verify cryptographic integrity hashes or signed release artifacts before installation. 3. Avoid commands that implicitly resolve the latest version of an executable package. 4. Use a verified package registry and enable provenance or signature verification where supported. 5. Vendor security-critical setup instructions into the audited Skill when practical. 6. Require users to inspect downloaded Skill content before activation, particularly content that handles authentication or account setup. 7. Run installation in a restricted environment without access to production credentials, sensitive files, or privileged system paths. 8. Document the exact expected dependency versions and establish a controlled update and re-audit process.
