T08 · Insecure Dependencies
- Location
README.md:7- Finding
Unpinned Third-Party Skill Installation
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 7-10
Vulnerability Type: Supply-chain risk from mutable and unpinned remote dependencies
Risk Level: MediumComplete Code Snippet:
markdown ## Install ```bash npx skills add github:LeoGoat2004/create-agent-apptext ### Technical Analysis The documented installation command invokes the `skills` npm CLI through `npx` without specifying a fixed package version. It also installs the Skill from a GitHub repository reference that is not pinned to an immutable commit SHA or verified integrity digest. Both sources may therefore resolve to content that differs from the version reviewed during this audit. If the npm package, repository, maintainer account, release process, or default branch is compromised or modified, the same command could retrieve and install altered Skill instructions or additional files. Because agent Skill text can influence subsequent tool use and generated code, mutable installation sources create a meaningful supply-chain trust boundary. This is a distribution-time vulnerability rather than evidence that the currently audited repository contains a malicious payload. No embedded malicious scripts were found in the reviewed project. ### Attack Path 1. An attacker compromises the npm package used by `npx`, the GitHub maintainer account, or the referenced repository. 2. The attacker publishes a malicious package version or changes the repository's mutable default branch. 3. A user runs the documented installation command. 4. `npx` resolves an unpinned CLI version, and the installer resolves the GitHub reference without an immutable commit constraint. 5. The altered Skill is installed and later loaded by the agent. 6. Malicious instructions or files may then act within the permissions available to the agent, subject to host-level controls and user approval requirements. ### Impact Assessment Successful exploitation co ...[truncated 638 chars]- Remediation
View remediation
Remediation Suggestions
-
Pin the npm installer to a reviewed, exact version rather than relying on the version selected by
npx:bash npx --yes skills@<exact-reviewed-version> add github:LeoGoat2004/create-agent-app#<full-commit-sha>Confirm that the installer supports commit-qualified GitHub references before publishing this syntax.
-
Pin the Skill source to a full immutable Git commit SHA, not a branch, tag, or default repository reference.
-
Publish checksums or signed release artifacts and document how users should verify integrity before activation.
-
Prefer a verified package or release channel with protected releases, mandatory multi-factor authentication, branch protection, and reviewed publishing workflows.
-
In automated environments, use a lockfile or equivalent installation manifest that records exact resolved versions and integrity metadata.
-
Advise users to inspect the downloaded Skill contents before enabling implicit invocation or granting filesystem, shell, network, browser, database, or secret access.
-
Add periodic dependency and provenance verification to the release process so that the documented command is tested against the exact reviewed artifacts.
-
