T08 · Insecure Dependencies
- Location
README.md:21- Finding
Unpinned Third-Party Installer and Mutable Remote Skill Source
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 21–25
Vulnerability Type: Supply-chain exposure through unpinned dependencies
Risk Level: MediumVulnerable Code
markdown ## Install ```bash npx skills add https://github.com/finskills/technical-analyst --skill technical-analysttext ### Technical Analysis The documented installation process invokes the npm package `skills` through `npx` without specifying a package version or integrity hash. It also installs the skill from a mutable GitHub repository reference rather than a reviewed commit SHA or signed release. Consequently, the code and skill instructions installed by this command can differ from the content that was audited. A compromise of the npm package, its publisher account, the GitHub repository, or the repository's default branch could replace the expected installation behavior or skill content with attacker-controlled material. This is an insecure dependency and supply-chain practice. The reviewed files contain no evidence that the current package or repository is malicious; the risk arises because the installation command does not cryptographically bind installation to the reviewed versions. ### Attack Path 1. An attacker compromises the npm package publisher, the GitHub repository, or an associated maintainer account. 2. The attacker publishes a malicious version of the unpinned `skills` package or modifies the repository's mutable default branch. 3. A user runs the documented `npx skills add` command. 4. `npx` retrieves the currently resolved installer, and the installer retrieves the current repository content rather than the audited revision. 5. Attacker-controlled installation logic or skill instructions are processed with the privileges available to the invoking user or agent. 6. Depending on the malicious replacement and the host's tool permissions, it could alter installed skill files, execute commands through t ...[truncated 783 chars]- Remediation
View remediation
Remediation Suggestions
- Pin the npm installer to a specifically reviewed version, for example by using
npx skills@<reviewed-version>. - Pin the GitHub source to an immutable commit SHA or a signed release rather than the repository's mutable default branch.
- Verify downloaded artifacts using a published cryptographic checksum or signature before installation.
- Record the reviewed installer version, repository commit, expected hashes, and verification procedure in the installation documentation.
- Run installation with the least-privileged account required and avoid exposing unrelated secrets in the installation environment.
- Prefer a package manager lockfile or another reproducible installation mechanism where supported.
- Periodically review pinned dependencies and update them only after security validation.
- Pin the npm installer to a specifically reviewed version, for example by using
