T08 · Insecure Dependencies
- Location
SKILL.md:15- Finding
Unpinned Remote Package Execution in Installation Instructions
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 15–17
Vulnerability Type: Insecure third-party dependency execution
Risk Level: MediumVulnerable Code Snippet:
bash npx skills add PaodingAI/skillsTechnical Analysis
The documented installation command invokes
npxwithout pinning theskillspackage to a specific audited version. Depending on the local environment and cache state,npxmay retrieve and immediately execute the latest package version from the configured package registry.The
PaodingAI/skillssource reference is also not pinned to an immutable commit or content digest. Consequently, both the installer implementation and installed repository content may change after this audit. The project provides no lockfile, integrity hash, signature verification procedure, or immutable revision in the installation command.This creates a supply-chain risk: compromise of the package publisher, registry account, package namespace, upstream repository, or a future malicious release could cause code not covered by this audit to execute during installation.
Attack Path
- An attacker compromises the publisher account, package namespace, configured registry, or referenced upstream source.
- The attacker publishes or substitutes a malicious version while retaining the expected package or repository name.
- A user follows the installation command in
SKILL.md. npxresolves mutable remote content because no version or integrity constraint is specified.- The downloaded installer runs malicious code with the privileges of the user executing the command.
- The malicious installer could access files and credentials available to that user, alter installed Skill content, or execute additional commands.
Impact Assessment
Successful exploitation could provide arbitrary code execution under the installing user's account. The accessible scope would include files, environm ...[truncated 411 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the
skillspackage to a specific audited version rather than relying on the latest registry release. - Pin
PaodingAI/skillsto an immutable commit hash or signed release tag. - Use a lockfile and package-manager integrity metadata where applicable.
- Verify package signatures or cryptographic checksums before executing downloaded code.
- Document the expected package registry and trusted upstream repository to reduce dependency-confusion risk.
- Prefer installing dependencies in a restricted environment with least privilege and without unnecessary production credentials.
- Establish a controlled update process in which new installer and Skill revisions are reviewed before updating pinned versions.
- Pin the
