T08 · Insecure Dependencies
- Location
SKILL.md:26- Finding
Unpinned Third-Party Plugin Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 26-28
Vulnerability Type: Unpinned external dependency installation
Risk Level: Mediumtext - GitHub repository: `https://github.com/Sheygoodbai/nojargon` - Plugin install: `openclaw plugins install clawhub:@sheygoodbai/openclaw-nojargon` - Enable plugin: `openclaw plugins enable nojargon`Technical Analysis
The skill instructs users or agents to install and enable a mutable third-party plugin without specifying an immutable version, commit, checksum, or cryptographic signature. The audited project contains only the discovery document and does not include the plugin implementation, so the behavior of the installed dependency cannot be verified from this artifact.
Because the installation command does not pin an audited release, it may retrieve a newer package than the one originally reviewed. Compromise of the package publisher, registry entry, distribution infrastructure, or a future release could introduce attacker-controlled behavior through this supply-chain boundary.
The document states that the plugin uses hooks to steer reply generation and rewrite outgoing text. These capabilities are consistent with its advertised purpose, but they also mean that a compromised release could affect generated or delivered content.
Attack Path
- An attacker compromises the third-party package publisher, registry entry, release process, or distribution account.
- The attacker publishes a malicious release under the referenced package identity.
- A user or agent follows the unpinned installation command in
SKILL.md. - OpenClaw resolves and installs the currently available package rather than a previously audited immutable release.
- The user enables the plugin.
- The malicious dependency executes through the plugin hooks available to it and can manipulate processing within the scope of those hooks.
Impact Assessment
Successful ex ...[truncated 665 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the plugin to a specific audited version or, preferably, an immutable source commit.
- Publish and verify a cryptographic checksum or trusted signature before installation.
- Configure the package source to reject unexpected publishers, package identities, or unsigned releases.
- Review the plugin source and release artifacts before enabling it.
- Document the plugin hooks, filesystem access, network access, credentials, and other permissions it requires.
- Apply least privilege so the plugin can access only the reply-processing functionality required for plain-language rewriting.
- Use a lockfile or equivalent reproducible dependency manifest where supported.
- Establish a controlled update process that requires security review before changing the pinned version.
