T08 · Insecure Dependencies
- Location
SKILL.md:182- Finding
Unpinned Package Execution in Setup Instructions
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 182-183; equivalent unpinned commands are also referenced at lines 173, 177, 248, and 249
Vulnerability Type: Supply-chain risk caused by unpinned dependency retrieval and execution
Risk Level: Mediumbash 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 invoke
npxwithout pinning an exact version or integrity digest for theskillspackage. The referencedAgentPMT/agent-skillssource is also not pinned to a reviewed commit or immutable release in these commands.npxmay retrieve and execute package code from the configured npm registry. Consequently, the code executed when a user follows these instructions can differ from the code available when this Skill was audited. The reviewed project contains no lockfile, checksum, vendored setup utility, or other mechanism that establishes an immutable dependency set.This is a supply-chain weakness rather than evidence that the current dependency is malicious. Exploitation requires compromise or malicious modification of a package, publisher account, registry resolution path, or referenced upstream source.
Attack Path
- An attacker compromises the publisher account, npm package, registry resolution path, or referenced upstream Skill repository.
- The attacker publishes or serves a modified version containing malicious installation or runtime behavior.
- A user follows the documented setup instructions and runs the unpinned
npx skills add ...command. npxresolves and executes the attacker-controlled package version.- The malicious package operates with the permissions of the user running the command and may alter files, access user-readable data, invoke network services, or install additional components.
Impact Assessment
Successful e ...[truncated 682 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the executable npm package to an exact reviewed version, for example by using an explicit version rather than allowing
npxto resolve the latest release. - Pin
AgentPMT/agent-skillsto an immutable commit hash or cryptographically verified release instead of a mutable branch or repository reference. - Publish and verify integrity hashes or signed provenance for all downloaded setup artifacts.
- Use a lockfile or a vetted, vendored installer so the dependency graph remains reproducible.
- Instruct users to verify the package publisher, version, signature, and expected checksum before execution.
- Avoid running installation commands with administrator or root privileges; use an isolated, least-privileged environment.
- Add dependency monitoring and periodically review pinned versions before intentionally updating them.
- Pin the executable npm package to an exact reviewed version, for example by using an explicit version rather than allowing