T08 · Insecure Dependencies
- Location
SKILL.md:13- Finding
Unpinned Third-Party Plugin Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 13
Vulnerability Type: Unpinned third-party dependency
Risk Level: MediumVulnerable Code
text 1. **安装插件**: `openclaw plugins install openclaw-morphixai`Technical Analysis
The installation command references the
openclaw-morphixaiplugin without pinning a reviewed version, immutable checksum, or signed artifact. As a result, the component installed by users can change after this skill has been reviewed.Because the plugin mediates access to the MorphixAI service and a linked GitHub account, compromise of its publisher account, package repository, or release process could cause users to install attacker-controlled code. The audit found no evidence that the current plugin is malicious; the finding concerns the mutable and unverifiable dependency installation process documented by the skill.
Attack Path
- An attacker compromises the plugin publisher, package repository, or distribution channel.
- The attacker publishes a modified release under the expected
openclaw-morphixaipackage name. - A user follows the prerequisite command in
SKILL.md. - The package manager resolves the unversioned name to the attacker-controlled release.
- The malicious plugin executes with the permissions of the OpenClaw process.
- Depending on available credentials and granted scopes, it may access the MorphixAI API key or misuse the linked GitHub authorization.
Impact Assessment
Successful exploitation could allow arbitrary behavior within the security context of the OpenClaw process. Potential impact includes exposure of locally available credentials, unauthorized operations against linked GitHub repositories, modification of issues or pull requests, and triggering of GitHub Actions workflows. The exact repository scope and privileges depend on the permissions granted to the linked GitHub integration and the host environment.
- Remediation
View remediation
Remediation Suggestions
- Pin the plugin to a specific, reviewed version rather than resolving an unversioned latest release.
- Prefer an immutable artifact identified by a cryptographic digest.
- Verify package signatures or checksums before installation and fail closed if verification fails.
- Document the approved package registry, publisher identity, and expected artifact hash.
- Establish a controlled dependency-update process that includes security review before changing the pinned version.
- Grant the linked GitHub integration only the repository access and API scopes strictly required for intended operations.
- Keep production deployment permissions and sensitive GitHub Actions environments subject to independent approval controls.
