T08 · Insecure Dependencies
- Location
SKILL.md:5- Finding
Unpinned Executable Installed from a Third-Party Homebrew Tap
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 5
Vulnerability Type: Unpinned third-party supply-chain dependency
Risk Level: MediumComplete Code Snippet:
yaml metadata: {"clawdbot":{"emoji":"🧾","requires":{"bins":["summarize"]},"install":[{"id":"brew","kind":"brew","formula":"steipete/tap/summarize","bins":["summarize"],"label":"Install summarize (brew)"}]}}Technical Analysis
The skill declares
summarizeas a required executable and instructs the host to install it from the external Homebrew tapsteipete/tap. The dependency is not constrained to a reviewed version, immutable commit, checksum, or cryptographic signature.Consequently, the two audited project files do not establish the precise implementation that will be installed and executed. The effective behavior can change independently of this skill package if the tap, formula, source archive, or distribution infrastructure is modified. Because no executable source is bundled, the installed CLI's implementation and data-handling behavior could not be reviewed as part of this audit.
This is a supply-chain exposure rather than evidence that the current upstream package is malicious.
Attack Path
- An attacker compromises the referenced Homebrew tap, its maintainer account, formula source, or an upstream artifact used by the formula.
- The attacker publishes a modified formula or executable while retaining the expected
summarizepackage and binary names. - A host follows the skill's installation metadata and installs the dependency without an immutable version or independently verified integrity constraint.
- The agent invokes the substituted
summarizeexecutable on a URL or local file. - The attacker-controlled executable runs with the invoking user's privileges and can access data and credentials available to that process.
Impact Assessment
Successful exploitation could permit arbitrary code execution with the privileges of the user who i ...[truncated 616 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the dependency to a reviewed, immutable release or source commit rather than relying on a mutable formula reference.
- Verify the downloaded artifact using an independently published cryptographic checksum or signature before installation.
- Prefer an official, trusted distribution channel with signed releases and transparent provenance.
- Record the reviewed dependency version, source repository, expected digest, and update procedure in the skill metadata or documentation.
- Review the dependency's installation scripts and executable source before approving updates.
- Run the CLI with least privilege and expose only the files and environment variables required for the current operation.
- Avoid passing unrelated secrets into the CLI process; use narrowly scoped provider credentials where supported.
- Document whether local content is transmitted to external AI, extraction, or YouTube-processing services so users can make an informed data-handling decision.
