T08 · Insecure Dependencies
- Location
SKILL.md:126- Finding
Unpinned Third-Party Installation Commands Create a Supply-Chain Risk
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 126-127
Vulnerability Type: Unpinned third-party dependencies and installation sources
Risk Level: MediumVulnerable Code:
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 setup instructions execute an npm-distributed command and install skills from a moving repository reference without pinning a package version, repository commit, integrity digest, or trusted signature. The effective content installed or executed when a user follows these instructions can therefore differ from the content available during this audit.
This does not establish that the current dependencies are malicious. However, it creates a supply-chain trust boundary in which compromise of the npm package, source repository, publisher account, or distribution infrastructure could introduce unreviewed behavior.
Attack Path
- An attacker compromises the npm package, upstream repository, or a publisher account used by the installation process.
- The attacker publishes or references a modified package or Skill containing unintended behavior.
- A user follows the documented unpinned
npx skills addinstructions. - The installation process retrieves the attacker-controlled current version rather than an audited immutable version.
- Malicious installation logic or Skill content executes or is installed with the permissions available to the invoking user.
Impact Assessment
The exact impact depends on the behavior and privileges of the external installer and installed Skills, which are not included in this project. If the retrieved component executes locally, it may obtain the invoking user's filesystem, environment, network, and process privileges. It could also alter Agent behavior through subsequently loaded Skill instructions. No such m ...[truncated 150 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the npm package or command-line utility to a reviewed version.
- Pin the AgentPMT repository to an immutable commit hash or signed release tag.
- Publish cryptographic checksums or signatures and verify them before installation.
- Avoid executing latest-version package content directly through
npx. - Vendor the required setup instructions or dependencies where practical so their contents can be audited with this Skill.
- Document the permissions and local effects of the installer before asking users to run it.
- Require a separate review whenever the pinned dependency version or repository commit changes.
