T08 · Insecure Dependencies
- Location
README.md:37- Finding
Unpinned executable package installation through a mutable registry tag
- Content
View full analysis
Vulnerability Details
File Location:
README.md, line 37
Vulnerability Type: Unpinned third-party executable dependency
Risk Level: Mediumbash npx clawhub@latest install rm-safetyTechnical Analysis
The recommended installation command uses
npxwith the mutablelatesttag. This causes package content selected by the registry at installation time to be downloaded and executed. The effective installer can therefore differ from the version reviewed during this audit.The command provides no exact version constraint, package integrity value, signature verification, or other mechanism that binds installation to an audited artifact. If the package publisher account, registry entry, or a future package release is compromised, malicious package code or lifecycle behavior could run during installation.
This is a supply-chain weakness in the documented installation process. No malicious package content or malicious intent was identified in the audited project itself.
Attack Path
- An attacker compromises the
clawhubpackage publisher account or otherwise gains control over a release selected by thelatesttag. - The attacker publishes a modified package containing malicious installer or runtime behavior.
- The registry points the mutable
latesttag to that release. - A user follows the recommended
npx clawhub@latest install rm-safetyinstruction. npxretrieves and executes the attacker-controlled package.- The payload operates with the permissions of the user running the command.
Impact Assessment
Successful exploitation could allow arbitrary code execution with the installing user's privileges. Depending on those privileges and the host environment, the malicious package could read or modify user-accessible files, access environment variables and credentials, alter installed skills, or install additional dependencies.
The direct scope is limited to permissions available to the invoking user unless the ...[truncated 122 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace
@latestwith an exact, reviewed package version, for exampleclawhub@X.Y.Z. - Publish and verify a cryptographic checksum or signed provenance statement for the expected package artifact.
- Use a lockfile or equivalent integrity-pinning mechanism where supported.
- Document the expected package publisher, registry, version, and integrity value.
- Require a new security review before updating the pinned version.
- Consider instructing users to download and inspect a versioned package before executing it rather than relying on automatic execution through a mutable tag.
- Replace
