T08 · Insecure Dependencies
- Location
SKILL.md:39- Finding
Unpinned Third-Party Skill Installations Create a Supply-Chain Risk
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 39–51
Vulnerability Type: Unpinned third-party skill dependencies
Risk Level: MediumThe package directs users to install 11 externally hosted ClawHub skills without immutable version constraints, content digests, signatures, or canonical source references.
bash clawhub install einstein-research-backtest-dv clawhub install einstein-research-backtest-engine-dv clawhub install einstein-research-breadth-dv clawhub install einstein-research-bubble-dv clawhub install einstein-research-edge-dv clawhub install einstein-research-ftd-dv clawhub install einstein-research-options-dv clawhub install einstein-research-portfolio-risk-dv clawhub install einstein-research-regime-dv clawhub install einstein-research-scenario-dv clawhub install einstein-research-themes-dvTechnical Analysis
These commands resolve mutable package names through an external registry. The repository does not pin versions or content hashes and does not include the referenced skill implementations for local review. Consequently, the content installed by a user may differ over time from the content originally intended by the package author.
This is a supply-chain weakness rather than evidence that any referenced package is currently malicious. Exploitation would require compromise or malicious control of a referenced package, its publisher account, the registry, or the dependency-resolution process. Without integrity verification, users cannot reliably establish that downloaded skill content matches a previously audited artifact.
Attack Path
- An attacker compromises a referenced skill publisher account or the ClawHub distribution channel, or otherwise gains control over the package resolved by one of the listed names.
- The attacker publishes a modified skill under that package name.
- A user follows the documented quick-start procedure without specifying an imm ...[truncated 1031 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin every referenced skill to an immutable release version rather than resolving only by package name.
- Prefer content-addressed dependencies and verify cryptographic hashes before installation.
- Require signed releases and validate signatures against documented publisher identities.
- Publish canonical source repository and release links for each included skill.
- Audit and vendor the referenced skill contents when feasible so the reviewed implementation is distributed with the pack.
- Maintain a lock file recording exact versions, digests, and resolved sources.
- Add automated integrity and provenance checks to the installation workflow.
- Apply least-privilege permissions and sandboxing to all installed skills, especially those capable of filesystem, network, shell, or credential access.
- Document that users must review dependency changes before upgrading to newer releases.
