T08 · Insecure Dependencies
- Location
README.md:14- Finding
Unpinned Package Execution in Installation Instructions
- Content
View full analysis
Vulnerability Details
File Locations:
README.md:14README_CN.md:14
Vulnerability Type: Unpinned third-party package execution
Risk Level: MediumVulnerable Code
bash npx clawhub install maxhub-temp-mailTechnical Analysis
The installation instructions invoke
clawhubthroughnpxwithout specifying a reviewed package version, integrity hash, lockfile, registry, or publisher-verification mechanism. Consequently, the package selected and executed when a user follows these instructions may differ from the version available when this Skill was audited.This creates a supply-chain trust dependency on the package registry, the package publisher account, and the unresolved current package release. If any of those components are compromised, a malicious package version could be delivered through the documented installation command.
The issue is only triggered when a user manually executes the documented command; the reviewed Skill does not automatically run it.
Attack Path
- An attacker compromises the
clawhubpublisher account, package registry distribution path, or a transitive dependency used by the resolved package. - The attacker publishes or serves a malicious package version.
- A user follows the installation instructions and executes
npx clawhub install maxhub-temp-mail. npxresolves and downloads the unpinned package version.- Malicious package, lifecycle, dependency, or CLI code executes 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 permissions and host configuration, the malicious package could access user-readable files, environment variables, credentials, network resources, and project data or modify files writable by that user.
The instructions do not require administrative privileges, so privilege escalation is not inherent. The maxim ...[truncated 78 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
clawhubto a specific reviewed version:
bash npx clawhub@<verified-version> install maxhub-temp-mail- Document the expected package registry, canonical publisher, and package identity.
- Where supported, verify package signatures, provenance attestations, or integrity hashes before execution.
- Review and update the pinned version through a controlled dependency-update process rather than resolving the latest release at installation time.
- Apply the same corrected command to both
README.mdandREADME_CN.md. - Consider using an installation mechanism backed by a lockfile or other reproducible dependency manifest.
- Pin
