T08 · Insecure Dependencies
- Location
install.bat:3- Finding
Unpinned Remote Skill Installation
- Content
View full analysis
Vulnerability Details
File Location:
install.bat:3
Additional Location:README.md:14-17
Vulnerability Type: Unpinned third-party skill dependency
Risk Level: MediumVulnerable Code:
install.bat:3bat clawhub install english-phonetic-skillREADME.md:14-17bash clawhub install english-phonetic-skillTechnical Analysis
The installation command retrieves a remote registry package using only the mutable package name
english-phonetic-skill. It does not pin an immutable version or content digest and does not explicitly verify a package checksum, signature, or publisher identity.Consequently, the package installed by this command is not guaranteed to be identical to the locally audited project files. A later package release, registry compromise, publisher-account compromise, or package ownership transfer could cause the same command to install modified instructions, scripts, or other unreviewed content.
The issue is a supply-chain weakness rather than evidence that the package currently available from the registry is malicious.
Attack Path
- An attacker compromises the registry entry, publisher account, release process, or another component controlling the named package.
- The attacker publishes a modified release under the existing
english-phonetic-skillname. - A user downloads this project and executes
install.bat, or manually follows the equivalent command inREADME.md. clawhubresolves the mutable package name to the attacker-controlled release.- The unreviewed remote package is installed.
- The user restarts OpenClaw as instructed, causing the remotely obtained Skill content to be loaded and used.
Impact Assessment
Successful exploitation could replace the reviewed Skill with attacker-controlled Skill content. The resulting impact depends on the permissions and capabilities granted to installed Skills and the OpenClaw runtim ...[truncated 474 chars]
- Remediation
View remediation
Remediation Suggestions
- Prefer installing the locally audited artifact rather than resolving a separate remote package by name.
- If remote installation is required, pin an immutable package version and, where supported, a cryptographic content digest.
- Verify the package publisher's identity and require registry signature validation before installation.
- Publish and verify a SHA-256 or stronger checksum for the exact package archive.
- Configure the installer to fail closed if the expected version, digest, signature, or publisher identity does not match.
- Inspect the downloaded package contents before activation and confirm that they match the reviewed source.
- Record the locked package version and digest in both
install.batandREADME.mdso automated and manual installation procedures use the same verified artifact.
