T08 · Insecure Dependencies
- Location
SKILL.md:33- Finding
Unpinned Global Installation of a Credential-Handling Dependency
- Content
View full analysis
**路径别名:** 下文中 `$VISUAL` = `{OPENCLAW_HOME}/workspace/visual/` ## Core Workflow ... ### Preflight 1. `meitu --version` → 未安装则提示 `npm install -g meitu-cli` ``` ### Technical Analysis The Skill instructs users to install `meitu-cli` globally from the npm registry without specifying an exact reviewed version, integrity hash, lockfile, or verified distribution source. Although the documentation states that version 0.1.9 or later is required, the command does not enforce that constraint and normally resolves to the registry's current release. The installed CLI is subsequently entrusted with both Meitu API credentials and user-supplied portrait images. A compromised package release, compromised publisher account, or malicious dependency introduced into a later release could therefore execute under the user's account. npm packages may also run lifecycle scripts during installation, increasing exposure before the CLI is explicitly invoked. The audit did not find evidence that the named package is currently malicious. The vulnerability is the unsafe, mutable installation process and the level of trust granted to the resulting executable. ### Attack Path 1. An attacker compromises the npm package, its publisher account, or a transitive dependency used by a later release. 2. A user follows the Skill's instruction and runs `npm install -g meitu-cli`. 3. npm resolves and installs the attacker-controlled release because no exact version or integrity value is enforced. 4. Malicious code executes through an installation life ...[truncated 798 chars]- Remediation
View remediation
