T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:58
- Finding
- Unpinned Remote Dependency Execution via npx## Vulnerability Details **File Location**: `SKILL.md:58` **Vulnerability Type**: Unpinned third-party dependency execution **Risk Level**: Medium **Vulnerable Code**: ```markdown 10. **Report back**: skill path, the description verbatim, and the install command the user can run on other machines (`npx --yes github:dennisrongo/claude-skills install <name>` for library skills). ``` ### Technical Analysis The skill directs users to run a package directly from a mutable GitHub repository through `npx`. The dependency is not pinned to an immutable commit hash or verified release, so the code executed later may differ from the code that was originally reviewed. The `--yes` option also suppresses the package-installation confirmation prompt. This creates a supply-chain risk: compromise of the upstream repository, its maintainer account, or its default branch could replace the expected installer with malicious code. The vulnerability is classified as insecure dependency use rather than confirmed malicious behavior because the audited file contains no malicious payload and does not establish that the referenced repository is compromised. ### Attack Path 1. An attacker compromises the referenced GitHub repository or an account authorized to modify it. 2. The attacker adds malicious code to the repository revision resolved by the unpinned `npx` command. 3. The skill reports the documented installation command to a user. 4. The user runs `npx --yes github:dennisrongo/claude-skills install <name>`. 5. `npx` retrieves and executes the current upstream package without requiring installation confirmation. 6. The malicious package executes with the privileges and environmental access of the invoking user. ### Impact Assessment Successful exploitation permits arbitrary code execution under the invoking user's account. Depending on that account's privileges and environment, the payload could read or modify accessible project fil ...[truncated 404 chars]
- Remediation
- ## Remediation Suggestions - Pin the GitHub dependency to a reviewed, immutable commit hash rather than a mutable default branch. - Prefer a signed and versioned release whose provenance and integrity can be verified. - Remove `--yes` so users retain an explicit confirmation boundary before remote code is installed and executed. - Document the exact trusted revision and provide a verification procedure for its commit or release signature. - Prefer a locally audited installer or vendored, integrity-checked package when practical. - Re-audit and deliberately update the pinned revision when adopting upstream changes.