T08 · Insecure Dependencies
- Location
SKILL.md:13- Finding
Unpinned Third-Party CLI Installation from a Custom Homebrew Tap
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 13-17
Vulnerability Type: Unpinned third-party dependency from a mutable package source
Risk Level: MediumVulnerable Code
yaml install: - kind: brew formula: runapi-ai/tap/runapi bins: - runapiTechnical Analysis
The skill declares installation of the
runapiexecutable from the custom Homebrew taprunapi-ai/tapwithout pinning a reviewed version, release artifact, checksum, signature, or source commit. The audited project does not include the Homebrew formula or the CLI source code, so the executable installed through this instruction cannot be statically verified as part of the skill review.Because the package reference is mutable, its effective code can change after this skill has been audited. A compromise of the tap, its release infrastructure, or its maintainer account could cause subsequent installations to retrieve and execute attacker-controlled code.
The resulting CLI is especially security-sensitive because the skill directs it to process RunAPI authentication state and user-selected local media. This finding concerns dependency provenance and mutability; the audit found no evidence that the current package is malicious.
Attack Path
- An attacker compromises the custom Homebrew tap, its maintainer account, or an upstream release artifact referenced by its formula.
- The attacker publishes a modified formula or executable under the existing
runapi-ai/tap/runapipackage name. - An agent following the skill installs the dependency without validating a pinned version, checksum, or cryptographic signature.
- Homebrew installation hooks or a later
runapiinvocation execute the attacker-controlled payload with the permissions of the agent's operating-system account. - The payload can access data available to that process, potentially including RunAPI authentication material, saved CLI configuration, request data, and local media selected for ...[truncated 640 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the CLI to an explicitly reviewed version rather than installing the mutable latest package.
- Reference an immutable release artifact or source commit and verify its published cryptographic checksum or signature before installation.
- Document the canonical source repository and trusted release-signing identity so provenance can be independently validated.
- Pin the custom tap itself to a reviewed commit where the installation mechanism supports it.
- Refuse automatic installation when the expected version, checksum, signature, or source provenance cannot be verified.
- Run the CLI with least privilege and restrict its access to credentials and local files not required for the current task.
- Periodically review dependency updates before changing the pinned version.
