T08 · Insecure Dependencies
- Location
SKILL.md:36- Finding
Unpinned Third-Party Installation Through npx
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 36 and 39
Vulnerability Type: Supply-chain exposure through unpinned installer and dependency resolution
Risk Level: Mediumbash # ClawHub (recommended) npx skills install fangshan101-coder/fx-base # npm npx skills install fx-baseTechnical Analysis
Both installation commands invoke the unversioned
skillsnpm package throughnpx. If it is not already available locally,npxmay download and execute the currently resolved package. The commands also install an unversioned Skill using either a repository-style identifier or a short registry name.No exact package version, immutable commit hash, checksum, signature, lockfile, or other integrity control is specified. Therefore, the installer or installed Skill can change after this artifact has been reviewed. The short
fx-baseidentifier also depends on registry name resolution without documenting a verified publisher or canonical source.This finding concerns the documented installation workflow. The audited project itself contains no confirmed malicious payload.
Attack Path
- An attacker compromises the account, repository, release process, or registry package associated with the installer or target Skill.
- The attacker publishes a modified version containing malicious installation or runtime behavior.
- A user follows the documented unpinned
npx skills install ...command. npxresolves and executes the currently available installer package.- The installer resolves and installs the currently available target content without validating it against an audited immutable version or expected digest.
- The compromised code executes with the permissions of the user running the installation.
Impact Assessment
Successful exploitation could permit arbitrary code execution under the installing user's account. The resulting access would be limited by that account's ...[truncated 407 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the
skillsinstaller to an exact reviewed version rather than allowingnpxto resolve the latest release. - Pin the installed Skill to an immutable release version or commit hash.
- Publish cryptographic checksums or signatures and verify them before installation or execution.
- Document the canonical package publisher and source repository.
- Remove or clarify the ambiguous short-name installation command unless publisher identity and package provenance can be verified.
- Use lockfiles and reproducible installation procedures where the tooling supports them.
- Review pinned updates before changing the documented versions or integrity metadata.
- Pin the
