T08 · Insecure Dependencies
- Location
SKILL.md:7- Finding
Unpinned Third-Party Homebrew Dependency
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 7
Vulnerability Type: Supply-chain risk from a mutable third-party package source
Risk Level: MediumComplete Code Snippet:
yaml metadata: {"clawdbot":{"emoji":"🎮","requires":{"bins":["gog"],"install":[{"id":"brew","kind":"brew","formula":"steipete/tap/gogcli","bins":["gog"],"label":"Install gog (brew)"}]}}}Technical Analysis
The skill directs the environment to install
gogclifrom the third-party Homebrew tapsteipete/tap. The dependency declaration does not pin an immutable release, formula revision, source commit, or artifact checksum. Consequently, the code installed in the future can differ from what existed when this skill was reviewed.Because the project contains no local implementation of the CLI, its effective behavior cannot be verified from the audited package. If the external tap, formula, upstream release process, or referenced artifact is compromised, a modified dependency could execute attacker-controlled code during installation or later CLI invocation.
This risk is amplified by the documented workflow, which asks users to authorize the installed CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.
Attack Path
- An attacker compromises the third-party Homebrew tap, its maintainer account, the upstream release channel, or an artifact referenced by the formula.
- The attacker modifies the formula or distributed artifact to install a malicious
gogexecutable or run malicious installation logic. - The skill installation process resolves the mutable
steipete/tap/gogclidependency without validating a project-declared immutable version or checksum. - The user follows the documented setup and supplies OAuth client credentials or authorizes one or more Google Workspace services.
- The compromised executable runs with the invoking user's local privileges and may misuse the OAuth authorization available to ...[truncated 932 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the dependency to an immutable, reviewed release rather than relying only on the mutable formula name.
- Verify downloaded artifacts with a cryptographic checksum or signature tied to the pinned release.
- Record the authoritative upstream repository and expected release provenance in the skill metadata or documentation.
- Prefer a vendor-controlled, reproducible distribution channel where available, and review the Homebrew formula before enabling automated installation.
- Add dependency monitoring so formula ownership, source URLs, checksums, and release signatures are revalidated when versions change.
- Apply least privilege to OAuth authorization: request only the specific Google Workspace services and scopes required for the intended task.
- Store OAuth credentials in an operating-system credential store with restrictive permissions, and document procedures for reviewing and revoking granted access.
- In managed environments, install an independently verified binary through an approved internal package repository.
