T08 · Insecure Dependencies
- Location
SKILL.md:353- Finding
Unpinned Third-Party Setup Dependencies Enable Supply-Chain Compromise
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:353-369
Vulnerability Type: Unpinned and mutable third-party dependencies
Risk Level: MediumVulnerable Code
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-setuptext ### Technical Analysis The documented setup procedure retrieves and installs third-party tooling and skills without specifying an immutable package version, repository commit, or integrity digest. In particular, invoking `npx skills` may download and execute the version currently resolved by the package registry. The referenced AgentPMT skills are also selected by mutable names rather than reviewed immutable revisions. Consequently, the effective setup payload can change after this skill has been audited. Compromise of the npm package, package publisher, upstream repository, skill registry, or distribution account could cause users following these instructions to retrieve malicious content. The main project itself contains no embedded executable payload, and no evidence demonstrates that the current dependencies are malicious. The ...[truncated 1559 chars]- Remediation
View remediation
Remediation Suggestions
- Pin the npm installer package to a reviewed exact version rather than relying on the registry's current resolution.
- Pin each external skill to an immutable repository commit, signed release, or content-addressed artifact.
- Publish and verify cryptographic hashes or signatures before installation.
- Use package-lock or equivalent lock metadata where supported, and reject unexpected dependency changes.
- Disable or explicitly review package lifecycle scripts before allowing installation in a privileged environment.
- Download and inspect external skills before loading them into an agent session; do not automatically trust updated remote instructions.
- Run installation in a sandbox with minimal filesystem, network, credential, and environment-variable access.
- Require explicit user confirmation before downloading or executing dependencies.
- Document the expected publisher identity, package version, skill revision, and integrity value directly in
SKILL.md. - Prefer a verified first-party distribution channel and implement signed-release verification throughout the update process.
