T08 · Insecure Dependencies
- Location
SKILL.md:15- Finding
Unpinned Package Execution in Installation Instructions
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:15
Vulnerability Type:T08: Insecure Dependencies
Risk Level: MediumVulnerable Code:
bash npx clawhub install @Cortez_1/time-machineTechnical Analysis
The documented installation command invokes
clawhubthroughnpxwithout specifying an audited version or package integrity value. If the package is not already available locally,npxcan retrieve and execute the version currently resolved by the configured package registry.This means the code executed during installation is not fully constrained to the project content covered by this audit. A compromised upstream release, registry account, dependency chain, or unexpected future version could alter installation behavior after the skill has been reviewed.
Attack Path
- An attacker compromises the upstream
clawhubpackage, its publisher account, or a dependency used by the resolved release. - The attacker publishes a malicious version that is selected by the unpinned command.
- A user follows the installation command from
SKILL.md. npxretrieves and runs the unaudited package version.- Malicious installation code executes with the operating-system privileges of the user running the command.
Impact Assessment
Successful exploitation could allow arbitrary code execution under the installing user's privileges. Depending on that user's permissions and environment, the malicious package could access user-readable files, credentials, project data, environment variables, or modify files and local configuration. The affected scope is the system or execution environment in which the installation command is run; this project itself does not contain the hypothetical upstream payload.
- An attacker compromises the upstream
- Remediation
View remediation
Remediation Suggestions
- Pin the installer to a specifically reviewed version, for example by invoking
clawhubwith an explicit version. - Use a lockfile and package-manager integrity metadata where the installation workflow supports them.
- Document the expected official registry and package publisher so users can verify the source.
- Prefer a locally installed, locked development dependency over automatically downloading the latest CLI at execution time.
- Verify package signatures, checksums, or provenance attestations before executing downloaded installation tooling.
- Establish a release process that re-audits the installer and its dependency tree before updating the documented version.
- Pin the installer to a specifically reviewed version, for example by invoking
