T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:23
- Finding
- Unpinned Third-Party SDK Installation Creates a Supply-Chain Risk## Vulnerability Details **File Location**: `SKILL.md`, line 23 **Vulnerability Type**: `T08: Insecure Dependencies` **Risk Level**: Medium **Vulnerable Code**: ```bash pip install moltcanvas-sdk ``` ### Technical Analysis The installation instructions retrieve `moltcanvas-sdk` from the configured Python package index without specifying an exact version or verifying an integrity hash. The installed artifact is therefore mutable and may differ between installations. The SDK source is not included in the audited project, so its installation hooks and runtime behavior cannot be verified from the supplied artifact. If the package publisher, publishing credentials, package-index account, or distribution process were compromised, an attacker could distribute malicious code under a later release. Following the documented command would install that release without an explicit review or integrity check. Python packages may execute code during installation or when imported. In this Skill, the package is subsequently imported and supplied with API keys, image paths, wallet addresses, and transaction-related parameters, making dependency integrity particularly important. ### Attack Path 1. An attacker compromises the package publisher, publishing credentials, or distribution channel for `moltcanvas-sdk`. 2. The attacker publishes a malicious or backdoored version under the legitimate package name. 3. A user follows the Skill documentation and runs `pip install moltcanvas-sdk`. 4. Because no version or hash is specified, pip resolves and installs the attacker-controlled release. 5. Malicious code executes during package installation or when `moltcanvas` is imported. 6. The code operates with the privileges of the installing or executing user and may access data available to that process. ### Impact Assessment Successful exploitation could permit arbitrary code execution with the privileges of the user running pip or the agent ...[truncated 532 chars]
- Remediation
- ## Remediation Suggestions 1. Pin the SDK to a specific, reviewed version, for example: ```bash pip install moltcanvas-sdk==<reviewed-version> ``` 2. Provide a requirements or lock file containing cryptographic hashes, and require hash verification during installation: ```bash pip install --require-hashes -r requirements.txt ``` 3. Review the exact package release against the linked source repository and record the corresponding source commit and distribution hashes. 4. Use an isolated virtual environment or restricted container with least-privilege filesystem and network access. 5. Configure automated dependency monitoring and require security review before updating the pinned version. 6. Avoid exposing wallet secrets or unrelated credentials to the SDK process; provide only the minimum API credentials and filesystem access required.