T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:9
- Finding
- Unpinned Third-Party Package Execution## Vulnerability Details **File Location**: `SKILL.md`, lines 9–10 **Vulnerability Type**: Unpinned package retrieval, execution, and global installation **Risk Level**: Medium ### Vulnerable Code ```markdown - One-off run: `npx skilllens scan` (or `pnpm dlx skilllens scan`) - Global install: `pnpm add -g skilllens` ``` ### Technical Analysis The documented commands retrieve the latest available `skilllens` package from the configured package registry without specifying a reviewed version, lockfile, checksum, or other integrity control. Both `npx` and `pnpm dlx` can download and immediately execute package code. The global installation command additionally installs the unpinned package into the user's global package environment. This creates a supply-chain trust boundary in which the code executed by users can change after the skill has been reviewed. Package compromise, malicious ownership transfer, registry-account compromise, or an unsafe registry configuration could therefore introduce arbitrary code. The static pre-scan warning concerning `curl | bash` does not represent an actual remote-execution instruction in this project. The phrase appears only at `SKILL.md:39` as an example of behavior auditors should detect. ### Attack Path 1. An attacker compromises the package publisher, a package release, or the registry source used by the package manager. 2. The attacker publishes a malicious version under the expected `skilllens` package name. 3. A user or agent follows the documented unpinned `npx`, `pnpm dlx`, or global installation command. 4. The package manager retrieves the attacker-controlled release. 5. Package lifecycle hooks or CLI entry-point code execute with the privileges of the invoking user. 6. The malicious package can access resources available to that user and, for a global installation, leave package files or commands in the global package environment. ### Impact Assessment Successful exploitation could execute arbitrary code wit ...[truncated 653 chars]
- Remediation
- ## Remediation Suggestions 1. Pin the dependency to a specific reviewed version, for example by documenting `npx skilllens@<reviewed-version> scan`. 2. Prefer a project-local dependency recorded in a lockfile rather than downloading and executing the latest package on each use. 3. Verify package provenance through the official publisher, registry metadata, release signatures, or documented integrity hashes. 4. Remove or discourage global installation unless it is operationally necessary. 5. Require explicit user confirmation before downloading, installing, or executing third-party packages. 6. Run the tool with ordinary user privileges in a restricted environment that exposes only the target directory and required network access. 7. Establish an update-review process so new package versions are inspected and approved before changing the pinned version.