T08 · Insecure Dependencies
- Location
SKILL.md:66- Finding
Mutable Package Execution During Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:66
Vulnerability Type: Supply-chain risk caused by execution of an unpinned package version
Risk Level: HighVulnerable Code
bash npx clawhub@latest install harenaTechnical Analysis
The installation instructions invoke
npxwith the mutablelatesttag. If the package is not already cached locally,npxcan download it from the configured package registry and execute it immediately.The effective code executed by this command can therefore change after the Skill has been reviewed. The package version and integrity digest are not pinned, and the documentation does not require users to inspect or verify the downloaded package before execution. This introduces a supply-chain trust boundary that is broader than necessary because the MCP server can also be configured directly without executing a package fetched at installation time.
This is an insecure dependency practice rather than evidence that the currently published package is malicious.
Attack Path
- An attacker compromises the
clawhubpackage, its publishing credentials, the associated registry account, or another component of the package distribution chain. - The attacker publishes a malicious release and causes it to resolve through the
latesttag. - A user follows the documented installation command.
npxdownloads and executes the attacker-controlled package.- The malicious package executes with the operating-system privileges of the user running the installation.
Impact Assessment
Successful exploitation could permit arbitrary code execution with the installing user's privileges. Depending on those privileges and the local environment, the executed package could access user-readable files, environment variables, API credentials, agent configuration, and network resources or modify user-owned files.
The Skill does not itself request elevated privileges, a ...[truncated 208 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace the mutable
latesttag with an explicitly audited package version. - Pin and verify an integrity digest where the installation mechanism supports it.
- Document the expected package registry and package publisher identity.
- Prefer manual MCP configuration because it avoids executing an installer package.
- If an installer remains necessary, document how users can download and inspect it before execution.
- Add an update process that requires security review before changing the pinned package version.
- Warn users not to run the installation command with administrative or root privileges.
- Replace the mutable
