T08 · Insecure Dependencies
- Location
SKILL.md:8- Finding
Unpinned Third-Party Homebrew Tap Creates a Supply-Chain Risk
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 8–17
Vulnerability Type: Unpinned third-party dependency
Risk Level: MediumVulnerable code:
json "openclaw": { "emoji": "📸", "requires": { "bins": ["camsnap"] }, "install": [ { "id": "brew", "kind": "brew", "formula": "steipete/tap/camsnap",Technical Analysis
The installation metadata directs the agent to install
camsnapfrom the third-party Homebrew tapsteipete/tap. It does not pin a reviewed package version, formula commit, artifact digest, or signature.Because the named formula is mutable, the code installed in the future may differ from the code reviewed when this Skill was published. Installation consequently depends on the continued integrity of the tap repository, its maintainer accounts, the package hosting infrastructure, and any upstream artifacts downloaded by the formula.
This is a supply-chain weakness rather than evidence that the current package is malicious. Nevertheless, compromise of any trusted distribution component could turn the documented installation process into a remote code-execution path.
Attack Path
- An attacker compromises the third-party tap, a maintainer account, the upstream release infrastructure, or another component trusted by the formula.
- The attacker modifies the formula or its referenced artifact to distribute a malicious package.
- A user or agent follows the Skill installation metadata and resolves the mutable formula.
- Homebrew downloads and installs the attacker-controlled content.
- Installation logic or the resulting
camsnapexecutable runs with the privileges of the account performing installation.
Impact Assessment
Successful exploitation could execute arbitrary code with the privileges of the installing user. Depending on that account's permissions, the attacker could read or modify ...[truncated 303 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin installation to a specific, reviewed
camsnaprelease and immutable formula revision. - Verify downloaded artifacts using a published cryptographic checksum and, where available, a release signature or provenance attestation.
- Prefer an official, trusted package repository over a mutable third-party tap.
- Document the expected package version and integrity value so deployments can detect unexpected changes.
- Review the Homebrew formula for additional mutable downloads, install-time scripts, and insufficient integrity verification.
- Use a controlled internal mirror or allowlisted artifact repository for security-sensitive deployments.
- Run installation with the least-privileged account necessary and avoid administrative privileges unless they are explicitly required.
- Pin installation to a specific, reviewed
