T08 · Insecure Dependencies
- Location
SKILL.md:22- Finding
Unpinned Third-Party Plugin and Skill Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 22–23
Vulnerability Type: Unpinned third-party dependencies
Risk Level: MediumThe installation instructions use mutable package identifiers without specifying trusted versions or immutable integrity hashes:
sh openclaw plugins install clawhub:postlake openclaw skills install @postlake/postlake-publishTechnical Analysis
Both commands resolve and install third-party components at installation time. Neither dependency is constrained to an audited version or verified against a documented cryptographic digest. Consequently, the code installed by a future user can differ from the code that was available when this skill was reviewed.
If the registry, publisher account, package namespace, or dependency release process is compromised, an attacker could distribute a modified plugin or skill through the same legitimate-looking identifiers. This is a supply-chain weakness; the audited
SKILL.mditself does not contain evidence that the referenced packages are currently malicious.Attack Path
- An attacker compromises the package publisher, registry, namespace, or release pipeline associated with one of the referenced dependencies.
- The attacker publishes a malicious release under the existing package identifier.
- A user or agent follows the documented installation commands.
- OpenClaw resolves the mutable identifier to the compromised release because no audited version or digest is specified.
- The malicious component executes when installed or invoked, subject to the permissions and capabilities granted to the OpenClaw process and component.
Impact Assessment
A compromised dependency could execute with the privileges available to the OpenClaw runtime. Depending on the host configuration and permissions granted to the installed component, this could expose local files, authentication material, connected social-media capabilities, ...[truncated 310 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin each plugin and skill to a specific, reviewed version supported by the package manager.
- Where supported, lock dependencies to immutable content digests or verified checksums rather than tags or mutable package names alone.
- Document the expected publisher identity and require signature or provenance verification before installation.
- Maintain a lockfile or equivalent dependency manifest in the project so installations are reproducible.
- Review dependency release notes and package contents before updating pinned versions.
- Run installed components with least privilege, restricting filesystem, credential, network, profile, and social-account access to only what is necessary.
- Use a trusted internal mirror or allowlist for approved plugin and skill artifacts in sensitive environments.
