T08 · Insecure Dependencies
- Location
SKILL.md:34- Finding
Unpinned Third-Party Plugin Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 34–37 and 48–50
Vulnerability Type: Unpinned and unauditable third-party dependency
Risk Level: MediumVulnerable Code
yaml install: - id: openclaw-notfair kind: node label: "NotFair Meta Ads Plugin"text openclaw plugins install clawhub:openclaw-notfair openclaw plugins enable openclaw-notfair openclaw config set 'plugins.entries.openclaw-notfair.config.mcpUrl' '"https://notfair.co/api/mcp/meta_ads"' --strict-jsonTechnical Analysis
The documented installation command references
clawhub:openclaw-notfairwithout an immutable version, commit, integrity hash, or signed artifact. The plugin implementation is not included in the audited project, so its executable behavior and enforcement of the documented approval model cannot be verified fromSKILL.md.This creates a supply-chain risk: the effective code installed by users may change after this skill has been reviewed. Compromise of the package registry entry, publisher account, distribution infrastructure, or a future release could cause users to install code different from the reviewed instructions.
The configured hosted MCP endpoint further places authenticated advertising operations behind components that are not available in this project for inspection. This is disclosed and consistent with the skill's purpose, but it increases the consequences of dependency compromise.
Attack Path
- An attacker compromises the plugin publisher account, package entry, or distribution infrastructure, or publishes a malicious mutable update.
- A user follows the documented unversioned installation command.
- OpenClaw resolves and installs the attacker-controlled plugin version.
- The user enables the plugin and authenticates it for the NotFair and Meta Ads workflow.
- The malicious plugin abuses its execution context or authenticated advertising access to co ...[truncated 853 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the plugin to an immutable, reviewed version rather than installing an unspecified current release.
- Publish and verify a cryptographic integrity hash or signed provenance for the exact artifact.
- Include the plugin source in the review scope or link the installation to a reproducible, immutable source commit.
- Document the plugin's requested host permissions, credential access, data transmission, and MCP authorization boundaries.
- Grant the plugin and associated tokens only the minimum Meta Ads permissions required for the requested task.
- Enforce approval for money-affecting writes in a trusted local authorization layer rather than relying solely on the remote plugin or MCP service.
- Separate read-only and write-capable credentials where supported, and keep write access disabled until explicitly needed.
- Monitor installed artifact integrity and require review before accepting dependency updates.
