T08 · Insecure Dependencies
- Location
SKILL.md:14- Finding
Unpinned Third-Party CLI Installation Creates Supply-Chain Risk
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 14–18
Vulnerability Type: Unpinned dependency from a third-party Homebrew tap
Risk Level: MediumComplete Code Snippet:
yaml install: - kind: brew formula: runapi-ai/tap/runapi bins: - runapiTechnical Analysis
The skill requires the
runapiexecutable to be installed from the third-partyrunapi-ai/tapHomebrew tap without specifying an immutable version, formula revision, source commit, checksum, or signature. Consequently, the dependency retrieved during installation may differ from the version originally reviewed.The installed executable is subsequently trusted to handle authentication, read and upload local media, submit potentially billable tasks, and retrieve generated artifacts. The skill does not independently establish the integrity or provenance of that executable. This creates a supply-chain trust boundary in which compromise of the tap, formula, release artifact, or associated distribution infrastructure could introduce attacker-controlled native code.
Attack Path
- An attacker compromises the third-party Homebrew tap, formula repository, release account, or artifact hosting infrastructure.
- The attacker publishes a malicious or backdoored
runapirelease while retaining the expected formula and executable names. - An Agent following the skill installs or upgrades
runapi-ai/tap/runapiwithout enforcing an immutable reviewed version or verifying an artifact digest. - Homebrew executes installation logic and places the attacker-controlled
runapibinary on the local system. - During normal skill execution, the malicious binary receives access to authentication context, request data, local media paths, and service responses.
- The binary can exfiltrate accessible data or manipulate submitted tasks and downloaded results under the invoking user's privileges.
Impact Assessment
Successful e ...[truncated 691 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the CLI to a specifically reviewed version and, where supported, an immutable Homebrew formula revision or source commit.
- Publish and verify a cryptographic checksum for the expected release artifact before trusting or executing it.
- Prefer signed release artifacts and verify signatures against a documented, trusted maintainer key.
- Document the canonical tap repository, release source, expected version, and artifact digest so substitutions can be detected.
- Prevent silent or automatic upgrades from replacing the reviewed executable with a newer unreviewed version.
- Fail closed when the installed CLI version or digest does not match the approved value.
- Run the CLI with least privilege and restrict its access to unrelated credentials and files where practical.
- Require manual review when dependency integrity cannot be established rather than automatically installing the mutable formula.
