T08 · Insecure Dependencies
- Location
README.md:22- Finding
Unpinned Third-Party Installer and Mutable Remote Skill Source
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 22–26
Vulnerability Type: Supply-chain risk caused by unpinned third-party dependencies
Risk Level: MediumVulnerable Code:
bash ## Install ```bash npx skills add https://github.com/finskills/sector-rotation-analyst --skill sector-rotation-analysttext ### Technical Analysis The installation command invokes `npx skills` without specifying an audited package version. Depending on the local npm configuration and cache state, `npx` can download and execute the latest available version of the `skills` package. That version may differ from the version reviewed by the project maintainers and may include executable package or lifecycle behavior. The GitHub repository is also referenced without an immutable commit hash or signed release tag. Consequently, the content installed by the command can change after this audit even though the documented URL remains unchanged. Trusting both an unpinned npm package and a mutable repository reference creates a supply-chain exposure. A compromised package publisher, npm package, repository account, or repository branch could alter the installer or installed skill after review. ### Attack Path 1. An attacker compromises the npm package publisher, the package distribution channel, the GitHub repository, or an account authorized to modify the repository. 2. The attacker publishes a malicious version of the installer or modifies the repository content referenced by the installation command. 3. A user follows the documented installation procedure and runs the unpinned `npx skills add ...` command. 4. `npx` resolves the attacker-controlled package version, or the installer retrieves the modified repository content. 5. Malicious installer behavior may execute during installation, or altered skill instructions may be installed and subsequently loaded by the agent. ### Impact Assessment Malicious installer ...[truncated 598 chars]- Remediation
View remediation
Remediation Suggestions
- Pin the
skillsnpm package to a specific reviewed version, for example by using an exact version rather than allowingnpxto resolve the latest release. - Pin the GitHub source to an immutable, reviewed commit hash or a cryptographically verified signed release.
- Record and verify expected integrity information, such as the package-lock entry, npm integrity hash, release checksum, or signed provenance attestation.
- Prefer a trusted, locally installed installer whose version is controlled through a lockfile.
- Disable package lifecycle scripts during dependency acquisition where supported and where they are not required.
- Perform installation in a sandbox or least-privileged environment without production credentials or sensitive environment variables.
- Add an update-review process so changes to either the installer version or pinned repository revision require a fresh security review before deployment.
- Pin the
