T08 · Insecure Dependencies
- Location
SKILL.md:5- Finding
Unpinned Executable Third-Party Dependencies
- Content
View full analysis
`pip install super-dev` → `openclaw plugins install @super-dev/openclaw-plugin` ``` ### Technical Analysis The Skill instructs users to install the executable `super-dev` Python package and the `@super-dev/openclaw-plugin` package without pinning either dependency to an exact version or integrity digest. Consequently, the effective code installed by these commands can change after this Skill has been reviewed. Neither dependency's implementation is included in the audited project. Their installation-time and runtime behavior therefore cannot be verified from this repository. This creates a supply-chain trust boundary in which a compromised publisher account, malicious replacement release, dependency confusion event, or unexpectedly changed upstream version could introduce arbitrary executable behavior. ### Attack Path 1. An attacker compromises an upstream publisher, distribution account, package source, or dependency release process. 2. The attacker publishes a malicious version under the referenced package name. 3. A user follows the Skill's unversioned installation instructions. 4. The package manager resolves the installation to the attacker-controlled or compromised release. 5. Malicious installation hooks or runtime code execute when the package is installed, the plugin is loaded, or its tools are invoked. 6. The payload operates with the permissions of the user running OpenClaw or the installation command. ### Impact Assessment A malicious dependency could potentially: - Read or modify project files available to the in ...[truncated 590 chars]- Remediation
View remediation
