T08 · Insecure Dependencies
- Location
SKILL.md:218- Finding
Unpinned Third-Party Skill Installation Creates a Mutable Supply-Chain Risk
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 218-232
Vulnerability Type: Unpinned third-party dependency installation
Risk Level: MediumVulnerable Code
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-setuptext ### Technical Analysis The Skill instructs users or agents to invoke an unpinned npm command and install Skill content from a mutable third-party repository. The version of the `skills` npm package is not fixed, and the `AgentPMT/agent-skills` source is not pinned to a reviewed commit hash or signed release. Consequently, the content executed or installed when these commands are used can differ from what existed when this project was audited. The `npx` invocation executes package code during installation, while the installed Skills may introduce additional instructions, tool access, or executable components outside the reviewed two-file artifact. The installation is not automatically performed by this Skill, which limits immediate exploitability. Exploitation requires a user or an agent to follow the documented setup instructions. ### Attack Path 1. An attacker compromises the npm package, its publisher account, ...[truncated 1425 chars]- Remediation
View remediation
Remediation Suggestions
- Pin the npm CLI to a specifically reviewed version, for example by replacing an unversioned
npx skillsinvocation with an explicitly versioned package reference. - Pin
AgentPMT/agent-skillsto an immutable commit hash or cryptographically signed release rather than resolving the repository's current state. - Publish and verify SHA-256 checksums or signed provenance for all downloaded Skill artifacts.
- Require users to inspect the resolved package version, repository revision, manifests, instructions, and scripts before activation.
- Use npm lockfiles and integrity metadata where the installation workflow supports them.
- Run installation in a sandbox with minimal filesystem access, no unnecessary credentials, and restricted outbound network access.
- Avoid directing an agent to install dependencies autonomously. Require explicit user confirmation before downloading, executing, or activating external content.
- Prefer vendoring reviewed setup documentation or dependencies into the release when feasible, followed by a security review of the vendored content.
- Pin the npm CLI to a specifically reviewed version, for example by replacing an unversioned
