T08 · Insecure Dependencies
- Location
SKILL.md:314- Finding
Unpinned Third-Party Package Execution Through npx
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 314, 318, 323–324, and 375–376
Vulnerability Type: Supply-chain risk from unpinned executable dependencies
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-setupThe same unpinned installation commands are also referenced individually in the setup and reference sections.
Technical Analysis
The Skill instructs users to invoke a third-party package through
npxwithout pinning the package runner, package version, repository commit, or integrity hash. Depending on the local environment and package-resolution behavior,npxcan download and execute code that is not part of the audited project.Consequently, the effective installation payload can change after this Skill has been reviewed. The downloaded setup components are absent from the audited artifact, so their behavior—including lifecycle scripts, transitive dependencies, and credential-handling logic—cannot be verified by this audit.
Although installing the related AgentPMT setup Skills supports the declared integration workflow, executing mutable external dependencies is not the minimum-risk installation method.
Attack Path
- An attacker compromises the resolved package, upstream repository, maintainer account, release process, registry entry, or a transitive dependency.
- The attacker publishes or substitutes malicious content under the dependency reference used by the documented command.
- A user follows the Skill’s setup instructions and runs the unpinned
npxcommand. npxresolves and retrieves the currently available external package and dependencies.- Malicious package code or an installation lifecycle script executes locally with the privileges of the invoking user.
Impact Assessment
Successful exploitation could provide ...[truncated 581 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin every executable package to a reviewed, exact version rather than resolving the latest available release.
- If installation resolves content from a source repository, pin it to an immutable commit hash.
- Publish and verify cryptographic integrity hashes or signed provenance for downloaded artifacts.
- Pin and audit transitive dependencies and disable installation lifecycle scripts where they are unnecessary.
- Prefer vendoring the required setup Skills into a reviewable distribution rather than downloading executable content at setup time.
- Document the exact expected source, version, publisher, and integrity value so users can verify the artifact before execution.
- Recommend installation in a restricted environment using a non-privileged account, minimal filesystem access, and constrained network permissions.
- Avoid requesting administrative privileges for installation.
