T08 · Insecure Dependencies
- Location
SKILL.md:30- Finding
Unpinned Third-Party Skill Installation from a Mutable Remote Source
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 30-36
Vulnerability Type: Unverified and unpinned third-party dependency installation
Risk Level: HighVulnerable Code
markdown 1. Execute `openclaw skills list` and check whether the output contains `byted-web-search`. 2. If installed: continue normally. 3. If not installed: execute `npx skills add https://skills.volces.com/skills/bytedance/agentkit-samples -s byted-web-search --agent openclaw` - If installation succeeds: continue normally. - If installation fails: **do not terminate the entire briefing**. Record that "web search is unavailable," skip the web-search portion in Step 2, generate the briefing using notification information only, and state at the end that external information could not be searched.Technical Analysis
The Skill directs the Agent to install executable third-party Skill content from a mutable remote URL whenever
byted-web-searchis absent. The command does not pin an immutable release, version, or commit and does not verify a checksum, cryptographic signature, publisher identity, or expected package contents.Consequently, the content installed at execution time can differ from the content that was originally reviewed. The installation is also performed automatically without requesting explicit user authorization after the missing dependency is detected. If the remote source, distribution service, repository, or publisher account is compromised, malicious content could be delivered through this trusted installation path.
This is a supply-chain vulnerability rather than evidence that the current upstream package is malicious. The risk arises because the Skill automatically trusts mutable remote content and may execute it with the permissions available to the OpenClaw Agent.
Attack Path
- An attacker compromises the upstream Skill source, its publisher account, the hosting service, or another c ...[truncated 1753 chars]
- Remediation
View remediation
Remediation Suggestions
-
Pin an immutable dependency revision
- Reference a specific reviewed release or commit hash instead of a mutable repository URL.
- Prevent automatic resolution to the latest available upstream content.
-
Verify integrity and authenticity
- Publish and validate a cryptographic checksum for the exact Skill artifact.
- Prefer signed releases and verify the signature against a trusted publisher key.
- Fail safely if identity or integrity verification cannot be completed.
-
Require explicit installation approval
- Inform the user that a third-party Skill is missing and identify its source, requested version, and required permissions.
- Require affirmative user approval before downloading or installing it.
- Do not combine dependency installation and immediate execution without an intervening trust decision.
-
Review and restrict the dependency
- Audit the pinned dependency before deployment.
- Grant only the network, file, notification, and tool permissions required for web search.
- Run the dependency in a sandbox with outbound-network restrictions and limited filesystem access.
-
Use a trusted dependency registry or allowlist
- Install only dependencies whose publisher and immutable artifact are approved by the deployment administrator.
- Maintain an allowlist containing expected package identifiers, versions, hashes, and signing identities.
-
Preserve the existing safe degradation path
- If the verified dependency is unavailable, skip external search and generate the briefing from local notification results.
- Clearly disclose that external search was omitted rather than installing unverified content automatically.
-
