T08 · Insecure Dependencies
- Location
README.md:6- Finding
Execution of an Unpinned Third-Party Package
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 6–8
Vulnerability Type: Unpinned dependency execution through a mutable release tag
Risk Level: Mediumbash npx clawhub@latest install gratitude-trackerTechnical Analysis
The documented installation command instructs
npxto retrieve and execute the package identified by the mutablelatesttag. The project does not pin an exact reviewed version, specify an integrity hash, provide a lockfile, or otherwise constrain the package artifact that will execute.Because the
latesttag can be reassigned whenever a new package version is published, the code executed by this command can change after this skill has been reviewed. This creates a supply-chain trust boundary between the documented project and the external package registry.Attack Path
- An attacker compromises the
clawhubpackage, its maintainer account, or the relevant package publication channel. - The attacker publishes a malicious package release and assigns it to the
latesttag. - A user follows the installation command from
README.md. npxdownloads the attacker-controlled release from the configured package registry.- Package lifecycle scripts or the invoked package entry point execute with the privileges of the user running the command.
Impact Assessment
Successful exploitation could permit arbitrary code execution under the installing user's account. Depending on that account's privileges and environment, the malicious package could access user-readable files, environment variables, credentials available to the process, network resources, and writable project or user directories.
The documented command does not itself request elevated privileges, so system-wide administrative access is not established by the available evidence. The impact is limited initially to the permissions and accessible resources of the invoking process, although exposed credentials or insecure local configurati ...[truncated 35 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace the mutable
latesttag with an exact, reviewed package version, for example:bash npx clawhub@<reviewed-exact-version> install gratitude-tracker - Verify the selected package artifact against a trusted integrity hash or package signature before execution.
- Use a lockfile where applicable and commit it to source control so dependency resolution is reproducible.
- Document the expected package registry and avoid fallback to untrusted or user-controlled registries.
- Review package lifecycle scripts and the resolved dependency tree before recommending the command.
- Run installation with the least-privileged user in an isolated environment when practical.
- Establish a controlled update process in which newer versions are reviewed before the documented version is changed.
- Replace the mutable
