T08 · Insecure Dependencies
- Location
SKILL.md:44- Finding
Unpinned Third-Party Homebrew Dependency
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 44–45
Vulnerability Type: Unpinned third-party package installation
Risk Level: MediumVulnerable Code
bash brew tap Mininglamp-AI/tap brew install mano-asrThe installed executable is subsequently invoked, including at
SKILL.md:78:bash mano-asr startTechnical Analysis
The installation instructions add a third-party Homebrew tap and install its
mano-asrpackage without pinning an immutable version, formula revision, commit, signature, or expected artifact checksum. The resulting executable is then run with the invoking user's privileges. Its startup process is also documented as automatically downloading an ASR model.Although the tap's organization name is consistent with the declared upstream project, the retrieved formula and artifacts remain mutable after this Skill has been reviewed. Consequently, a compromise of the tap, upstream release infrastructure, maintainer account, or distribution artifact could turn these documented commands into a supply-chain code-execution path.
Attack Path
- An attacker compromises the third-party Homebrew tap, its maintainer account, the upstream release infrastructure, or a referenced package artifact.
- The attacker modifies the formula or distributed artifact to include malicious code.
- A user follows the Skill's instructions and runs
brew tap Mininglamp-AI/tapandbrew install mano-asr. - Homebrew retrieves and installs the altered dependency because the instructions provide no immutable version or independently verified checksum.
- The user runs
mano-asr start, or OpenClaw invokes the installedmano-asrCLI during transcription. - The malicious payload executes locally with the permissions of the user running the command.
Impact Assessment
Successful exploitation could provide arbitrary code execution under the invoking user's account. The atta ...[truncated 425 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
mano-asrto a reviewed release and an immutable Homebrew formula revision or repository commit. - Publish and verify expected SHA-256 checksums for downloaded release artifacts and model files.
- Prefer signed releases and document signature verification against a trusted maintainer key.
- Review the third-party formula and all URLs it references before installation.
- Avoid relying on a mutable tap head or automatically changing artifact location.
- Run the transcription component with least privilege and restrict its access to only the required model directory and temporary audio files.
- Document that users should re-verify hashes and signatures before upgrades rather than automatically trusting newly published versions.
- If automatic model retrieval cannot be eliminated, pin the model identifier and revision and verify its integrity before loading it.
- Pin
