T08 · Insecure Dependencies
- Location
SKILL.md:182- Finding
Execution of Unpinned and Unverified External Components
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:182-185, 290, 326; equivalent instructions inSKILL_cn.md:182-185, 287, 322
Vulnerability Type: Third-party dependency and executable supply-chain risk
Risk Level: HighVulnerable Code
bash python3 {mosp_root}/kmc_standalone.py \ --xyz OUTPUT/{task_dir}/ini.xyz \ --json OUTPUT/{task_dir}/input.json \ --out-dir {task_dir}text - **mosp-for-chatMOSP** — KMC engine (cloned, includes main.exe)text If a required companion skill is unavailable, ask the user to install the missing ChatMOSP skill from ClawHub before continuing. Use the GitHub repository only as a fallback.Technical Analysis
The Skill directs the agent to execute an externally installed
kmc_standalone.pyscript, which in turn runs a native Windowsmain.exethrough Wine. It also instructs users to install companion Skills from ClawHub or, as a fallback, GitHub.No canonical repository URL, immutable commit identifier, release version, cryptographic checksum, package signature, or verification procedure is specified for these components. The reviewed package therefore cannot establish the provenance or integrity of the code that will ultimately execute.
This is a supply-chain weakness rather than evidence that the current package contains malicious code. However, because the unverified dependency includes Python code and a native executable, compromise, repository takeover, dependency substitution, or installation of a similarly named package could result in arbitrary code execution.
Attack Path
- An attacker compromises the external repository, distribution account, or package associated with
mosp-for-chatMOSPor a companion Skill. - Alternatively, the attacker publishes a similarly named repository or package and induces the user or agent to install it.
- The user or agent clones or installs the dependency without validating an immuta ...[truncated 929 chars]
- An attacker compromises the external repository, distribution account, or package associated with
- Remediation
View remediation
Remediation Suggestions
- Specify the canonical HTTPS repository and publisher identity for every external dependency.
- Pin
mosp-for-chatMOSPand all companion Skills to immutable commit hashes or signed release versions. - Publish and verify SHA-256 or stronger checksums for
kmc_standalone.py,engine/main.exe, and other executable components before each first use or update. - Prefer signed releases and validate signatures against a documented trusted public key.
- Reject execution if the dependency version, signature, or checksum does not match the approved manifest.
- Vendor reviewed dependencies where licensing permits, or audit the exact pinned source and executable artifacts separately.
- Run the simulation in a sandbox or container with restricted filesystem access, no unnecessary credentials, and limited network connectivity.
- Pin companion Skill versions instead of installing packages solely by name.
- Require explicit user confirmation before downloading, updating, or replacing executable dependencies.
