T08 · Insecure Dependencies
- Location
SKILL.md:84- Finding
Unpinned Remote Plugin Installation Creates a Supply-Chain Risk
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 84–88
Vulnerability Type: Unpinned third-party plugin installation
Risk Level: MediumVulnerable Code
bash openclaw plugins install clawhub:@openclaw/diagnostics-otelTechnical Analysis
The documented command installs
@openclaw/diagnostics-otelfrom a remote package source without specifying an immutable version, source revision, or integrity digest. Consequently, the code installed when a user follows the instructions may differ from the code that existed when this skill was reviewed.The project contains no plugin implementation, lockfile, checksum, signature-verification instructions, or other mechanism that establishes the identity and integrity of the downloaded artifact. If the registry account, package, distribution infrastructure, or mutable release is compromised, the installation command could retrieve attacker-controlled code.
Attack Path
- An attacker compromises the plugin publisher account, package registry, distribution channel, or mutable package release.
- The attacker publishes a modified
@openclaw/diagnostics-otelpackage containing malicious code. - A user follows the installation command in
SKILL.md. - OpenClaw resolves and downloads the attacker-controlled package because no immutable version or digest is required.
- The plugin executes in the OpenClaw environment and gains access available to that plugin process.
Impact Assessment
A compromised plugin could execute code with the privileges of the OpenClaw process. Depending on the host configuration, this may permit access to OpenClaw configuration, environment variables such as
LATITUDE_API_KEYandLATITUDE_PROJECT, locally accessible data, and telemetry processed by the plugin. It could also alter or exfiltrate agent trace data and make network requests using the process's available connectivity.The exact host-wide impact depends o ...[truncated 146 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the plugin to a reviewed, immutable version rather than relying on mutable package resolution.
- Where supported, require a cryptographic integrity digest or verified publisher signature.
- Document the authoritative registry and source repository so users can validate package provenance.
- Maintain a lockfile or equivalent artifact manifest recording the exact reviewed version and hash.
- Verify the downloaded artifact before installation and reject any digest or signature mismatch.
- Run the plugin under least privilege with restricted filesystem, environment-variable, and network access.
- Review and update the pinned version through a controlled dependency-update process rather than automatically consuming new releases.
