T08 · Insecure Dependencies
- Location
SKILL.md:6- Finding
Unpinned Executable Dependency from a Third-Party Homebrew Tap
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 6
Vulnerability Type:T08: Insecure Dependencies
Risk Level: MediumVulnerable Code
yaml metadata: {"clawdbot":{"emoji":"💎","requires":{"bins":["obsidian-cli"]},"install":[{"id":"brew","kind":"brew","formula":"yakitrak/yakitrak/obsidian-cli","bins":["obsidian-cli"],"label":"Install obsidian-cli (brew)"}]}}Technical Analysis
The skill directs the environment to install the
obsidian-cliexecutable from the third-party Homebrew tapyakitrak/yakitrak. The dependency is not pinned to an immutable version or commit, and no integrity checksum or signature is specified.Consequently, the code installed during a future setup may differ from the dependency implicitly reviewed when this skill was published. If the tap, its maintainer account, its source repository, or its release infrastructure is compromised, its formula could be modified to install or execute attacker-controlled code. This is a supply-chain trust risk; the audit did not establish that the current package is malicious.
Attack Path
- An attacker compromises the third-party Homebrew tap, a maintainer account, or an upstream artifact referenced by its formula.
- The attacker modifies the mutable formula or package artifact to include malicious installation or runtime behavior.
- A user installs the skill dependency through the declared
brewinstallation entry. - Homebrew retrieves and processes the compromised formula or artifact.
- The malicious dependency executes during installation or when the agent invokes
obsidian-cli. - The code operates with the permissions of the user running Homebrew or the agent and can target resources accessible to that account.
Impact Assessment
Successful exploitation could execute arbitrary code with the invoking user's privileges. The compromised CLI could read, alter, or delete accessible Obsidian notes and configuratio ...[truncated 368 chars]
- Remediation
View remediation
Remediation Suggestions
- Prefer an official, publisher-verified distribution channel for
obsidian-cli. - Pin the dependency to an immutable, reviewed release version or source commit rather than a mutable formula reference.
- Verify downloaded artifacts with a cryptographic checksum or signature anchored to a trusted publisher key.
- Audit and lock the Homebrew formula and all upstream download URLs before deployment.
- Document that
yakitrak/yakitrakis a third-party trust boundary and provide its verified source repository and maintainer information. - Run the CLI with least privilege and restrict its filesystem access to explicitly selected Obsidian vaults where practical.
- Monitor dependency updates and require security review before changing the pinned version or integrity metadata.
- Prefer an official, publisher-verified distribution channel for
