T08 · Insecure Dependencies
- Location
README.md:9- Finding
Unpinned Third-Party Installer and Mutable Skill Source
- Content
View full analysis
Vulnerability Details
File Location:
README.md:9-12; also documented inSKILL.md:31-34
Vulnerability Type: Supply-chain risk caused by unpinned external installation sources
Risk Level: MediumVulnerable Code
README.md:9-12:bash **Via npx skills:** ```bash npx skills add BarbaraLedbettergq/background-remover-claw-skilltext Equivalent installation guidance appears in `SKILL.md:31-34`: ```bash ## Install ```bash npx skills add BarbaraLedbettergq/background-remover-claw-skilltext ### Technical Analysis The documented installation command invokes an npm-resolved `skills` CLI without specifying a package version and retrieves a GitHub-hosted Skill without pinning a commit hash, immutable release, checksum, or cryptographic signature. Consequently, the code installed in the future is not guaranteed to match the code reviewed during this audit. This does not establish that the current installer or repository is malicious, but it creates a mutable supply-chain boundary through which compromised or unexpectedly changed content could be delivered. The issue is classified as an insecure dependency practice rather than remote payload execution in the audited runtime code: the examined JavaScript files do not download and execute remote source code themselves. ### Attack Path 1. An attacker compromises the npm package supplying the `skills` command, the referenced GitHub account/repository, or its release process. 2. The attacker publishes or replaces content with a malicious installer or Skill revision. 3. A user follows the documented unpinned `npx skills add` command. 4. The package manager resolves the current mutable package and repository content rather than the audited revision. 5. The malicious installation logic or Skill code executes with the privileges of the installing user. ### Impact Assessment Successful exploitation could permit arbitrary code executi ...[truncated 386 chars]- Remediation
View remediation
Remediation Suggestions
- Pin the
skillsCLI to a reviewed, exact version rather than allowingnpxto resolve the latest release. - Pin the Skill source to an immutable Git commit or signed release tag.
- Publish and verify a checksum or cryptographic signature for the downloaded Skill artifact.
- Use a trusted package registry identity and enable release protections such as multi-factor authentication and provenance attestations.
- Prefer a locked installation manifest that records all resolved versions and integrity hashes.
- Document how users can verify the source revision before installation.
- Pin the
