T08 · Insecure Dependencies
- Location
README.md:6- Finding
Unpinned Third-Party Package Execution via npx
- Content
View full analysis
Vulnerability Details
File Location:
README.md:6
Vulnerability Type: Unpinned executable dependency
Risk Level: Mediumbash npx clawhub@latest install password-managerTechnical Analysis
The documented installation command instructs users to download and execute the package currently associated with the mutable
latesttag. No exact version, integrity hash, lockfile, or package provenance verification is provided.Because the effective package content can change after this skill has been reviewed, a compromised maintainer account, package registry, or future package release could cause the command to execute code that was never included in this audit. This is a supply-chain risk rather than evidence that the package currently published as
clawhub@latestis malicious.Attack Path
- An attacker compromises the
clawhubpackage, its publisher account, its release pipeline, or the relevant package registry entry. - The attacker publishes a malicious release and assigns it the
latestdistribution tag. - A user follows the installation instruction in
README.md. npxretrieves the attacker-controlled package version and invokes its CLI or applicable installation behavior.- The malicious package executes with the permissions of the user running the command.
Impact Assessment
Successful exploitation could permit arbitrary code execution under the invoking user's account. Depending on that user's permissions and local environment, the package could access user-readable files, credentials, environment variables, developer tokens, and network resources; modify user-owned data or configuration; or install additional payloads. Administrative privileges are not inherently obtained by this command, but impact would increase if a user runs it from a privileged account or environment.
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace the mutable
latesttag with an exact, audited package version. - Document the expected registry and verified publisher identity.
- Provide a package integrity digest or signed provenance information and require verification before execution.
- Review the pinned package, including lifecycle scripts and transitive dependencies, before recommending it.
- Where supported, disable unnecessary package lifecycle scripts and use a lockfile or equivalent dependency integrity mechanism.
- Update the pinned version only through a controlled review process, followed by renewed security verification.
- Replace the mutable
