T08 · Insecure Dependencies
- Location
SKILL.md:11- Finding
Mutable Third-Party Package Is Downloaded and Executed During Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 11-13
Vulnerability Type: Unpinned remote package execution
Risk Level: Mediumbash npx clawhub@latest install openclaw-task-reminderTechnical Analysis
The documented installation command instructs users to execute the mutable
latestrelease of the third-partyclawhubpackage throughnpx. If the requested package is not already available locally,npxcan download it from the configured package registry and execute its code immediately.Because the command uses the
latestdistribution tag rather than an audited, immutable version, the code executed by future installations can differ from the code that was reviewed. The project does not provide a lockfile, package checksum, vendored installer, or other integrity control for this command. This creates a supply-chain trust boundary in which compromise of the package, publisher account, registry resolution, or release process can result in arbitrary code execution.This finding does not establish that the current
clawhubpackage is malicious; the vulnerability is the unsafe execution of a mutable and externally controlled package release.Attack Path
- An attacker compromises the
clawhubpublisher account, package publication pipeline, or another relevant package-distribution component. - The attacker publishes a malicious version and assigns it to the
latestdistribution tag. - A user follows the installation instructions in
SKILL.md. npxresolvesclawhub@latest, downloads the attacker-controlled release, and executes it.- The malicious package runs with the permissions and environment of the user performing the installation.
Impact Assessment
Successful exploitation permits arbitrary code execution with the privileges of the installing user. Depending on that user's permissions and environment, an attacker could read or modify accessible files, steal cr ...[truncated 399 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace
clawhub@latestwith a specifically reviewed and pinned version, for exampleclawhub@<exact-version>. - Verify the package's provenance and integrity before execution, using registry-supported signatures, attestations, or a published cryptographic digest where available.
- Document the expected package registry and trusted publisher identity to reduce dependency-confusion and registry-substitution risk.
- Prefer an installation process backed by a committed lockfile and integrity metadata when feasible.
- Review the resolved package and its transitive dependencies before updating the pinned version.
- Execute installation with the least-privileged user possible and avoid running it as an administrator or in an environment containing unnecessary secrets.
- Consider vendoring a reviewed installer or directing users to inspect downloaded code before execution if reproducible package verification is unavailable.
- Replace