T08 · Insecure Dependencies
- Location
SKILL.md:10- Finding
Unpinned Third-Party Installation Through npx
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 10–16
Vulnerability Type: Unpinned third-party dependency installation
Risk Level: MediumVulnerable Code
bash npx skills add pskoett/pskoett-ai-skillsbash npx skills add pskoett/pskoett-ai-skills/intent-framed-agentTechnical Analysis
The installation instructions invoke the third-party
skillsnpm CLI throughnpxwithout specifying an exact package version. They also identify external GitHub-hosted skill content without pinning it to an immutable commit hash or verified release.Consequently, the components executed or installed when a user follows these instructions may differ from those present when this audit was performed. This creates a supply-chain trust gap: compromise of the npm package, its maintainer account, the external repository, or its maintainer credentials could cause later installations to execute malicious package lifecycle behavior or install malicious skill instructions.
The audited file does not demonstrate that either upstream component is currently malicious. The finding concerns the unsafe use of mutable, unverified dependencies.
Attack Path
- An attacker compromises the referenced npm package, its publishing credentials, the external repository, or a relevant maintainer account.
- The attacker publishes a malicious version of the CLI or modifies the repository content resolved by the installation command.
- A user follows the documented command without an explicit version or immutable revision.
npxresolves and executes the mutable third-party CLI.- The CLI retrieves or installs the attacker-controlled repository content.
- Malicious installation-time code may run with the invoking user's privileges, or malicious skill instructions may subsequently influence agent sessions.
Impact Assessment
Successful exploitation could execute code with the privileges of the user running
npx. Depending on that user's envir ...[truncated 497 chars]- Remediation
View remediation
Remediation Suggestions
- Pin the
skillsnpm CLI to an exact, reviewed version, rather than allowingnpxto resolve a mutable release. - Pin the external repository dependency to a reviewed commit hash or cryptographically verified, immutable release.
- Provide expected integrity hashes or signed provenance for downloaded artifacts.
- Avoid automatic execution of newly downloaded packages where practical; separate retrieval, review, and execution.
- Recommend inspecting downloaded skill files and scripts before activation.
- Use lockfiles and trusted registries where supported, and enable dependency provenance or signature verification.
- Periodically review pinned versions for disclosed vulnerabilities and update them through a controlled security-review process.
- Pin the
