T08 · Insecure Dependencies
Error
- Location
- README.md:47
- Finding
- Unpinned Package Download and Execution via npx## Vulnerability Details **File Location**: `README.md:44-48` **Vulnerability Type**: Unpinned third-party package execution **Risk Level**: High ```bash ### Other agents ```bash npx skills add haah-ing/vibes-skill ``` ``` ### Technical Analysis The documented installation command invokes the `skills` package through `npx` without specifying a reviewed version or verifying package integrity. If the package is not already available locally, `npx` can retrieve its current release from the configured package registry and execute it with the privileges of the user performing the installation. The effective installer can therefore change after this project has been audited. Compromise of the package, its publisher account, the package registry, or a related supply-chain component could cause the command to execute behavior that is absent from the reviewed repository. ### Attack Path 1. An attacker compromises the package publisher, registry entry, or another part of the package distribution chain. 2. The attacker publishes a modified version of the unpinned `skills` package. 3. A user follows the installation instructions and runs `npx skills add haah-ing/vibes-skill`. 4. `npx` retrieves the current compromised package version. 5. The malicious package executes with the installing user's privileges and can perform operations permitted to that account. ### Impact Assessment Successful exploitation could execute arbitrary package lifecycle or installer code under the current user's account. Depending on that account's permissions and environment, this could expose user-readable files, modify local configuration, install additional components, alter agent skills, or access credentials available to the process. The reviewed repository itself does not contain such a payload; the risk arises from executing a mutable, unverified dependency.
- Remediation
- ## Remediation Suggestions - Pin the installer to a specific, reviewed package version rather than relying on the current registry release. - Use a lockfile and registry integrity metadata where the installation workflow supports them. - Publish the expected package digest and verify it before execution. - Prefer a manual installation method that downloads a specific audited artifact without executing a general-purpose package installer. - Document the exact trusted package publisher and registry. - Run installation in a least-privileged or isolated environment and review changes before activating the skill.