T08 · Insecure Dependencies
- Location
SKILL.md:25- Finding
Unpinned Third-Party Plugin Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 25–27
Vulnerability Type: Unpinned third-party dependency installation
Risk Level: MediumVulnerable Code Snippet:
markdown - GitHub repository: `https://github.com/Sheygoodbai/taskfit` - Plugin install: `openclaw plugins install clawhub:@sheygoodbai/openclaw-taskfit` - Enable plugin: `openclaw plugins enable taskfit`Technical Analysis
The documented installation command identifies the third-party plugin by package name but does not pin an audited version or immutable content digest. It also provides no checksum or signature-verification procedure. Consequently, the code installed when a user runs this command may differ from the code that was reviewed.
The potential supply-chain impact is elevated by the documented plugin behavior. Lines 35–38 state that the plugin uses hooks to rewrite the current request before agent planning while processing patterns derived from local task history. A compromised plugin release could therefore execute within the plugin environment and interfere with requests or access data available to those hooks.
This finding establishes unsafe dependency guidance, not that the referenced plugin is currently malicious or compromised.
Attack Path
- An attacker compromises the package publisher, distribution registry, repository, or release process.
- The attacker publishes a modified release under the same mutable package identifier.
- A user follows the unpinned installation command in
SKILL.md. - OpenClaw resolves and installs the modified package because no immutable version, digest, or verified artifact is specified.
- The user enables the plugin, activating its pre-planning hooks.
- Malicious plugin code can then operate within the permissions and data access granted by the OpenClaw plugin runtime.
Impact Assessment
Successful exploitation could allow attacker-controlled plugin code ...[truncated 341 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the plugin to a specific audited version and, where supported, an immutable artifact digest.
- Publish the expected cryptographic checksum and require verification before installation.
- Use signed releases and document signature verification against a trusted publisher key.
- Replace the mutable installation example with a command that resolves only the reviewed artifact.
- Document the plugin's required filesystem, network, history, and request-hook permissions.
- Apply least privilege and sandboxing to prevent plugin access beyond the functionality described.
- Establish an update-review process rather than automatically trusting newer releases under the same package identifier.
- Link to reproducible build information or a reviewed source revision corresponding exactly to the distributed artifact.
