T08 · Insecure Dependencies
- Location
SKILL.md:5- Finding
Unpinned Third-Party Homebrew Dependency
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 5
Vulnerability Type: Unpinned dependency from a third-party Homebrew tap
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 installation metadata directs users to install
gogclifrom the third-party Homebrew tapsteipete/tapwithout specifying a version, immutable revision, or expected checksum. Consequently, the component installed in the future may differ from the one available when this skill was audited.This creates a supply-chain trust boundary outside the reviewed project. If the tap, its maintainer account, the upstream release process, or a referenced binary artifact is compromised, Homebrew could install attacker-controlled content. No evidence in the audited files establishes that the current dependency is malicious; the confirmed issue is the lack of dependency pinning and integrity verification.
Attack Path
- An attacker compromises the third-party Homebrew tap, upstream release infrastructure, or maintainer credentials.
- The attacker modifies the formula or replaces an artifact referenced by it with a malicious version.
- A user follows the skill installation metadata and installs
steipete/tap/gogcli. - Homebrew processes the altered formula or installs the substituted executable under the user's privileges.
- When the user configures or invokes
gog, the malicious component can access local data available to that process, including OAuth-related material, and can misuse Google Workspace access granted to the CLI.
Impact Assessment
Successful exploitation could execute code with the privileges of the user running Homebrew. Because the documented CLI is authorized for Gmail, Calendar, Drive, Contacts, She ...[truncated 359 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the dependency to a reviewed, immutable release rather than relying on the tap's current formula state.
- Verify downloaded artifacts using a cryptographic checksum or signature tied to the approved release.
- Document the authoritative source repository and expected publisher identity so users can validate provenance.
- Prefer a trusted package source with reproducible release artifacts and verifiable build provenance.
- Review dependency updates before changing the approved version or checksum.
- Request only the Google OAuth services and scopes required for the user's intended tasks rather than enabling all documented services by default.
- Protect locally stored OAuth credentials with restrictive file permissions and revoke them immediately if dependency compromise is suspected.
