T08 · Insecure Dependencies
- Location
README.md:22- Finding
Unpinned Package Execution in Installation Command
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 22–26
Vulnerability Type: Unpinned third-party package execution
Risk Level: MediumVulnerable Code
bash ## Install ```bash npx skills add https://github.com/finskills/us-stock-analyzertext ### Technical Analysis The installation instructions invoke `npx skills` without specifying a reviewed package version or integrity hash. When the package is not already available locally, `npx` can retrieve the currently resolved version of the `skills` package from the configured package registry and execute its command-line entry point. Consequently, the code executed by this instruction is not fully determined by the audited repository. Its behavior can change after the skill has been reviewed. The command also directs the installer to retrieve content from a mutable Git repository without pinning a commit hash or immutable release artifact. This creates a supply-chain exposure in which compromise of the registry package, its publisher account, the configured package registry, or the referenced repository could result in execution of code that was not included in this audit. ### Attack Path 1. An attacker compromises the publisher account, distribution channel, or repository associated with one of the dynamically retrieved components. 2. The attacker publishes or introduces a malicious version while retaining the expected package or repository name. 3. A user follows the documented installation instructions and runs: ```bash npx skills add https://github.com/finskills/us-stock-analyzernpxresolves and executes the unpinned package version.- The malicious installer code runs with the privileges of the user who launched the command.
Impact Assessment
Successful exploitation could permit arbitrary code execution under the installing user's account. Depending on that account's privileges and environment, an attacker could access user-readable files and creden ...[truncated 416 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the installer package to an explicitly reviewed version:
bash npx --yes skills@<reviewed-version> add <source> - Pin the skill source to an immutable commit hash or signed release rather than a mutable repository branch.
- Publish and verify cryptographic checksums or signatures for installation artifacts.
- Document the expected package publisher and registry so users can verify package provenance before execution.
- Use a lockfile or similarly reproducible dependency mechanism where supported.
- Recommend installation from a non-privileged account and warn users not to expose unrelated CI or developer credentials during installation.
- Re-audit installer behavior whenever the pinned package version or source commit is updated.
- Pin the installer package to an explicitly reviewed version:
