T08 · Insecure Dependencies
Warning
- Location
- README.md:8
- Finding
- Unpinned Package Execution in the Documented Installation Command<![CDATA[ ## Vulnerability Details **File Location**: `README.md:8` **Vulnerability Type**: Unpinned third-party package and mutable Skill source **Risk Level**: Medium ### Vulnerable Code ```bash npx skills add kirorab/12306-skill ``` ### Technical Analysis The documented installation procedure invokes the `skills` package through `npx` without an exact package version. Depending on the local npm configuration and cache, `npx` can retrieve and execute the latest published version of that package. The referenced Skill is also identified by a mutable repository-style name rather than an immutable commit, signed release, or verified artifact digest. Consequently, the code executed during installation can differ from the code reviewed in this audit. This creates a supply-chain trust boundary involving both the npm package and the mutable Skill source. ### Attack Path 1. An attacker compromises the npm account, package distribution channel, or repository associated with the installation command. 2. The attacker publishes a malicious version of the `skills` package or replaces the mutable Skill content. 3. A user follows the installation command from the README. 4. `npx` downloads and runs the changed package with the privileges of the invoking user. 5. The malicious installer can perform arbitrary actions allowed by that user account. ### Impact Assessment Successful exploitation can provide arbitrary code execution under the installing user's privileges. The resulting scope may include access to user-readable files, environment variables, developer credentials, project files, and network resources. If the command is run by an administrator or inside a privileged automation environment, the impact expands to those privileges. The audited project itself does not demonstrate that the current upstream package is malicious; the risk arises because the installation procedure does not cryptographically or immutably bind execution to the reviewed version. ]]>
- Remediation
- <![CDATA[ ## Remediation Suggestions 1. Pin the installer package to an exact reviewed version, for example: ```bash npx --yes skills@<reviewed-exact-version> add <immutable-skill-reference> ``` 2. Pin the Skill source to an immutable release tag or, preferably, a full commit digest. 3. Publish and verify cryptographic checksums or signatures for installation artifacts. 4. Document the expected package name, version, source repository, and artifact digest. 5. Use a lockfile-backed installation workflow where possible. 6. Run installation with the least-privileged account required and avoid elevated administrative execution. ]]>