T08 · Insecure Dependencies
- Location
skill.md:33- Finding
Unpinned Third-Party Package Execution Through npx
- Content
View full analysis
Vulnerability Details
File Location:
skill.md, lines 33–36
Vulnerability Type: Unpinned and mutable third-party dependency execution
Risk Level: HighVulnerable Code
bash # Install via ClawHub (recommended) npx clawhub@latest install before-die-socialTechnical Analysis
The documented installation command invokes
npxwith the mutable@latestpackage tag. This causes the package version selected by the registry at execution time to be downloaded and run without an exact version constraint, integrity hash, signature verification, or review of the resolved artifact.Consequently, the effective code executed by this command can change after the skill has been audited. If the package publisher account, package distribution infrastructure, or a future release is compromised, the command can execute attacker-controlled package code or lifecycle behavior under the invoking user's account.
This is a supply-chain weakness classified as
T08: Insecure Dependencies. The audited file does not itself contain a malicious payload; exploitation depends on the externally resolved package becoming malicious or compromised.Attack Path
- An attacker compromises the
clawhubpackage, its publisher account, or the package distribution path, or publishes a malicious release that becomes the version referenced bylatest. - A user follows the recommended installation instructions and runs:
bash npx clawhub@latest install before-die-social npxresolves and downloads the current mutable release rather than a previously audited, fixed version.- Attacker-controlled package code or applicable package lifecycle behavior executes with the permissions of the user running the command.
- That code can access or modify resources available to the invoking account, subject to operating-system permissions and any sandboxing in effect.
Impact Assessment
Successful exploitation could provide arbitrary code execution wit ...[truncated 373 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace
@latestwith an exact, reviewed package version. - Verify the resolved package using a trusted integrity hash or cryptographic signature before execution.
- Publish the expected package name, version, checksum, and provenance in the installation instructions.
- Review the package and its transitive dependencies before recommending it.
- Disable package lifecycle scripts where compatible with the installation process.
- Run installation under a minimally privileged account or within a sandbox.
- Establish a controlled update process in which new versions are reviewed and checksums are updated deliberately rather than selected automatically.
- Replace
