T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:14
- Finding
- Unpinned Third-Party Plugin Installation## Vulnerability Details **File Location**: `SKILL.md:14` **Vulnerability Type**: Unpinned third-party dependency installation **Risk Level**: Medium ### Vulnerable Code ```markdown 1. **安装插件**: `openclaw plugins install openclaw-morphixai` ``` ### Technical Analysis The Skill instructs users to install the third-party `openclaw-morphixai` plugin without specifying an immutable version, package digest, trusted repository, or signature-verification procedure. Consequently, the dependency retrieved during installation may differ from the version originally reviewed. The plugin's implementation is not included in the audited project, so its behavior and integrity cannot be verified from this repository. This is a supply-chain risk rather than proof that the named plugin is currently malicious. ### Attack Path 1. An attacker compromises the plugin's publishing account, package registry entry, distribution channel, or upstream build process. 2. The attacker publishes a modified release under the same mutable package name. 3. A user follows the instruction at `SKILL.md:14`. 4. The installer retrieves and executes or activates the compromised plugin. 5. The plugin accesses data and credentials available through its runtime permissions, including the MorphixAI API key and connected integrations. ### Impact Assessment A compromised plugin could act with the permissions granted to the OpenClaw process and connected MorphixAI accounts. Depending on configured scopes, exposed resources may include GitLab or GitHub repositories and work items, Jira issues, Outlook or Gmail messages, task lists, and calendar events. Potential consequences include sensitive-data disclosure, credential theft, unauthorized API operations, and compromise of the local agent environment. The precise privilege and data scope depend on the plugin runtime, host permissions, API-key capabilities, and account authorization scopes.
- Remediation
- ## Remediation Suggestions - Pin the plugin to a specifically reviewed version or, preferably, an immutable package digest. - Document the plugin's official registry namespace and source repository to reduce dependency-confusion and typosquatting risk. - Verify package signatures or checksums before installation. - Maintain an allowlist of approved plugin publishers and versions. - Review the plugin source and release artifacts before approving upgrades. - Grant the API key and connected accounts only the scopes required to generate the report. - Separate especially sensitive integrations, such as email and source control, into independently revocable credentials. - Monitor dependency advisories and require explicit review before changing the pinned version.