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:T08: Insecure Dependencies
Risk Level: MediumCode 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
steipete/tap/summarizeas an installation source for the requiredsummarizeexecutable. This is a third-party Homebrew tap rather than an artifact whose implementation is included in the audited project.The dependency declaration does not pin an immutable package version, source commit, or cryptographic checksum. Consequently, the executable installed in the future may differ from the version intended or reviewed when the skill was published. Because the audited artifact contains only documentation and metadata, the behavior of the installed executable cannot be verified from this project.
This creates a supply-chain trust boundary: compromise of the tap, formula, upstream release location, or maintainer account could cause Homebrew to install attacker-controlled code. The skill also documents API-key environment variables and processing of local files, increasing the sensitivity of information potentially accessible to a compromised executable.
Attack Path
- An attacker compromises the third-party Homebrew tap, its maintainer account, the referenced upstream artifact, or another component of its distribution chain.
- The attacker changes the formula or distributed package so that it installs a malicious
summarizeexecutable. - A user or agent follows the skill metadata and installs
steipete/tap/summarize. - The malicious executable runs with the privileges of the user invoking Homebrew or the CLI.
- When invoked, it could read files explicitly supplied for summarization, inspect environment varia ...[truncated 1140 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace the third-party tap with an official, reviewed package source where one is available.
- Pin the dependency to an immutable release version or source commit rather than relying on a mutable formula reference.
- Verify downloaded artifacts using a documented SHA-256 checksum or a validated cryptographic signature.
- Record the upstream source repository and reviewed release in the skill metadata so auditors can trace the installed implementation.
- Require explicit user approval before installing external executable dependencies.
- Run the CLI with least privilege and avoid invoking Homebrew or the executable with administrative privileges.
- Provide only the API key required for the selected provider, preferably through a scoped and short-lived credential.
- Isolate processing of sensitive files, restrict outbound network access where practical, and review dependency updates before adoption.
