T08 · Insecure Dependencies
- Location
SKILL.md:16- Finding
Unverified and Mutable Third-Party Dependencies
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:16,SKILL.md:19-20, andSKILL.md:91
Vulnerability Type: Supply-chain risk from unverified third-party installation sources
Risk Level: MediumVulnerable Code
bash brew install bjdzliu/openclaw/wechat-auto-replybash brew tap bjdzliu/openclaw brew install wechat-auto-replybash pip3 install pyobjcTechnical Analysis
The Skill does not include the executable implementation of the advertised automation. Instead, it directs users to install the effective implementation from an externally maintained Homebrew tap and to install an unpinned Python dependency.
No immutable commit, exact package version, checksum, signature verification, lock file, or source-validation procedure is specified. The reviewed
SKILL.mdtherefore cannot guarantee that future installations retrieve the same code that existed at audit time.The Homebrew formula and package contents can include executable installation or runtime logic. If the external tap, its maintainer account, package publication process, or an upstream dependency is compromised, attacker-controlled code could be delivered to users without requiring changes to this repository. The unpinned
pip3 install pyobjccommand similarly permits dependency resolution to change over time, weakening reproducibility and supply-chain integrity.Attack Path
- A user follows the installation instructions in
SKILL.md. - Homebrew adds or accesses the external
bjdzliu/openclawtap, whilepipresolves the current available Python package and dependencies. - An attacker compromises an external maintainer account, repository, release process, or dependency source and publishes a modified formula or package.
- The package manager downloads and installs the modified content because no immutable version or artifact-integrity check is required.
- The malicious installation or runtime ...[truncated 897 chars]
- A user follows the installation instructions in
- Remediation
View remediation
Remediation Suggestions
- Include the complete executable implementation in the reviewed Skill package so its behavior can be audited alongside
SKILL.md. - Pin the Homebrew formula and Python dependencies to immutable, reviewed versions or commits.
- Publish cryptographic checksums or signatures for distributed artifacts and verify them before installation.
- Use a dependency lock file with hashes for Python packages rather than an unconstrained
pip3 install. - Document the canonical source repository, maintainers, release process, and expected artifact hashes.
- Add automated dependency scanning and release-integrity checks to the build pipeline.
- Minimize the permissions granted to the installed command and explain how users can review or revoke screen-recording and accessibility permissions.
- Require security review whenever a pinned dependency or external formula is updated.
- Include the complete executable implementation in the reviewed Skill package so its behavior can be audited alongside
