T08 · Insecure Dependencies
- Location
SKILL.md:244- Finding
Unpinned External Companion Skills from Insufficiently Specified Sources
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:244-259and the equivalent companion-skill instructions inSKILL_cn.md:244-259
Vulnerability Type: Unpinned third-party Skill dependencies
Risk Level: MediumVulnerable Code Snippet
markdown ## ChatMOSP Companion Skills This skill is part of the ChatMOSP skill set. For complete functionality, install the companion ChatMOSP skills from ClawHub when they are missing: - chatmosp-input-coordinator - chatmosp-parameter-builder - chatmosp-msr-generator - chatmosp-kmc-simulator - chatmosp-literature-search - chatmosp-file-organizer 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 users to install several external companion Skills without specifying immutable versions, verified publisher identities, exact repository URLs, commit hashes, signatures, or integrity checksums. The GitHub fallback is also not tied to a specific organization, repository, release, or commit.
Skill dependencies can contain executable scripts or authoritative instructions that are loaded into an Agent context. Resolving dependencies solely by mutable names creates a supply-chain trust gap: a compromised publisher account, replaced package, malicious namesake, dependency-confusion entry, or modified repository could supply content different from what was originally reviewed.
The project itself contains only documentation files, and the reviewed text does not automatically download or execute a payload. Exploitation therefore depends on a user or orchestration system following the installation recommendation. Nevertheless, the absence of source and version pinning leaves no reliable mechanism for ensuring that the installed dependency is the intended reviewed artifact.
Attack Path
- One of the named Cha ...[truncated 1420 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin every companion Skill to an immutable, reviewed version or content-addressed release.
- Identify the expected publisher and provide exact official ClawHub package URLs rather than dependency names alone.
- Replace the generic GitHub fallback with exact organization and repository URLs pinned to verified commit hashes.
- Publish cryptographic checksums or signed manifests for every approved dependency artifact.
- Verify package signatures, publisher identity, version, and checksum before installation or loading.
- Maintain an allowlist of approved dependency identifiers and reject namesakes or packages from alternate publishers.
- Require explicit user approval after displaying the resolved source, publisher, version, requested capabilities, and integrity result.
- Review companion Skill instructions and scripts before granting filesystem, shell, network, credential, or persistent-storage access.
- Run third-party Skills with least privilege and isolate them from unrelated files, credentials, tools, and network destinations.
- Record dependency provenance and verified hashes in a lockfile or equivalent manifest to make installations reproducible.
