T08 · Insecure Dependencies
- Location
SKILL.md:219- Finding
Unpinned Third-Party Setup Dependencies Enable Supply-Chain Compromise
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:219-229andSKILL.md:282-283
Vulnerability Type: Unpinned npm package and remote Skill dependencies
Risk Level: MediumVulnerable Code
markdown - 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 The same unpinned commands are repeated in the references at `SKILL.md:282-283`. ### Technical Analysis The documented setup procedure invokes the `skills` npm package through `npx` without pinning a reviewed package version. It also retrieves Skills from `AgentPMT/agent-skills` without identifying an immutable release, commit hash, checksum, or signature. Consequently, the components executed or installed when a user follows these instructions may differ from those available at audit time. A compromise of the npm package, repository, publishing account, dependency chain, or mutable default branch could introduce malicious code or instructions. These setup dependencies support account connectivity but are not part of the core science-query schema. Automatically executing mutable third-party installers therefore exceeds the minimum privileges needed merely to describe or validate the Skill's query parameters. ### Attack P ...[truncated 1776 chars]- Remediation
View remediation
Remediation Suggestions
- Pin the
skillsnpm package to an explicitly reviewed version rather than allowingnpxto resolve the latest release. - Pin
AgentPMT/agent-skillsto an immutable commit hash or signed release tag. - Publish and verify cryptographic checksums or signatures for all downloaded Skill content.
- Use npm lockfiles and integrity metadata where installation architecture permits.
- Avoid automatically executing remote installation tools. Separate download, inspection, and activation into distinct user-approved steps.
- Display the exact source, version, commit identifier, and requested permissions before installation.
- Run setup tooling in a sandbox with restricted filesystem access, no unnecessary secrets in the environment, and outbound network access limited to required hosts.
- Review installed setup Skills before activation and prevent them from overriding safety policies or accessing unrelated Agent state.
- Replace the instruction to reinstall based solely on document age with a signed update and verification process.
- Pin the
