T08 · Insecure Dependencies
- Location
SKILL.md:361- Finding
Unpinned Third-Party Skill Installation Creates a Supply-Chain Risk
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 361-377
Vulnerability Type: Unpinned third-party dependency installation
Risk Level: MediumThe Skill instructs users to install additional AgentPMT Skills from mutable external sources without pinning an immutable version, commit, or integrity digest.
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-setupTechnical Analysis
The installation commands resolve content from external package, repository, and Skill-distribution infrastructure at installation time. They do not specify an immutable package version, repository commit, signed release, or expected content digest. Consequently, the installed content can differ from the content available when this Skill was audited.
This is especially sensitive for the account setup dependency because it is intended to guide MCP or REST authentication. If the external source, publisher account, package registry, repository, or distribution channel were compromised, altered setup content could attempt to capture credentials, redirect API traffic, introduce ...[truncated 2092 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin every external package or Skill to an immutable, reviewed version and, where supported, a specific repository commit.
- Publish and verify cryptographic integrity hashes or signed manifests for downloaded Skill artifacts.
- Avoid relying on floating repository branches or package tags for security-sensitive setup instructions.
- Document the expected publisher identity, package source, version, commit, and checksum beside each installation command.
- Prefer a reviewed lockfile or bundled, signed setup dependency over runtime resolution from mutable external sources.
- Where the package manager permits it, disable lifecycle scripts and other unnecessary installation-time code execution.
- Require explicit user confirmation before installing external Skills, particularly account and credential-management Skills.
- Review the downloaded setup Skill before use and ensure that it does not request secrets through prompts or logs.
- Run installation with the minimum filesystem and system permissions necessary, without administrator privileges.
- Retain the existing warning not to place account secrets, wallet private keys, mnemonics, signatures, or payment headers in prompts or logs.