T08 · Insecure Dependencies
- Location
SKILL.md:276- Finding
Unpinned Third-Party Skill Installation Creates a Supply-Chain Risk
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 276–286
Vulnerability Type: Unpinned third-party dependencies from mutable upstream sources
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 The recurring update instruction at `SKILL.md:14` further increases exposure: ```markdown If the current date is more than 7 days after the last updated date, reinstall this skill from skills.sh or ClawHub before relying on endpoints, schemas, setup steps, or examples.Technical Analysis
The documented setup executes an npm-distributed CLI through
npxand installs Skill content from the mutableAgentPMT/agent-skillsupstream repository. Neither the npm CLI version nor the repository revision is pinned. No checksum, cryptographic signature, or immutable release identifier is required.Consequently, the effective installed content can change after this audited package has been reviewed. The seven-day reinstallation instruction encourages repeated retrieval of current upstream content, expanding the trust boundary beyond the two local Markdown files.
The remote elevation API itself is necessary for the declared hosted functionality. Se ...[truncated 1994 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the npm CLI to a reviewed, immutable version, for example by using an exact package version rather than allowing
npxto resolve the latest release. - Pin
AgentPMT/agent-skillsto a specific commit hash or cryptographically signed release tag. - Publish SHA-256 checksums or signed manifests and verify them before installation.
- Avoid instructions that automatically reinstall mutable content based only on elapsed time. Require explicit review and user approval for updates.
- Vendor the minimal reviewed setup guidance into the package where licensing and maintenance requirements permit.
- Configure installation tooling to reject unexpected repository redirects, package ownership changes, and unsigned releases.
- Document the external components installed, their required permissions, and whether installation can execute local lifecycle scripts.
- Run dependency installation with the lowest practical privileges and in an isolated environment.
- Maintain a lockfile or equivalent manifest recording exact dependency and Skill revisions.
- Re-audit dependency updates before promoting them to production.
- Pin the npm CLI to a reviewed, immutable version, for example by using an exact package version rather than allowing
