T08 · Insecure Dependencies
- Location
SKILL.md:12- Finding
Mandatory Installation of an Unpinned Third-Party Plugin
- Content
View full analysis
**⚠️ CORE DEPENDENCY (MUST INSTALL)** > Because OpenClaw needs the actual code to sync data to the cloud dashboard and send API requests, this skill acts as the "brain", but it requires the "hands". > > You MUST install the companion code plugin from NPM for this workflow to function: > ```bash > openclaw plugins install claw-kanban > ``` > *Get your free Dashboard API Key to see the visualization at: **https://webkanbanforopenclaw.vercel.app*** ``` ### Technical Analysis The skill requires installation of the `claw-kanban` NPM plugin by package name without specifying an immutable version, package integrity hash, verified source revision, or trusted publication key. Package-manager installation causes executable third-party code to be retrieved outside the reviewed skill package. The companion plugin's source is not included in the audited project. Consequently, its install hooks, runtime behavior, filesystem access, network operations, credential handling, and update behavior cannot be verified from this artifact. Even if the package is benign at review time, a compromised maintainer account, malicious future release, package takeover, or registry supply-chain incident could alter the code subsequently installed by users. ### Attack Path 1. An attacker compromises the package publisher, registry account, or upstream release process for `claw-kanban`. 2. The attacker publishes a malicious release under the same package name. 3. A user follows the skill's mandatory installation instruction without a pinned version or integrity verification. 4. OpenClaw retrieves and installs the attacker-controlled release. 5. Installation hooks or plugin initialization execute the malicious code with the permissions available to the OpenClaw process. 6. The malicious plug ...[truncated 636 chars]- Remediation
View remediation
