T08 · Insecure Dependencies
- Location
SKILL.md:252- Finding
Unverified External Skill Installation Instructions
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:252-269
Additional Location:SKILL.md:101
Vulnerability Type:T08: Insecure Dependencies
Risk Level: MediumVulnerable Code
bash # Install Duleheng Consulting (ClawHub) clawhub install duleheng-consulting # Install Duleheng Consulting (OpenClawmp) openclawmp install skill/[assetId] # Install Master Series (Engineering Cost) openclawmp install skill/4a3a9beaa9dc4a399d56b5a3a5063016 # Yin Yilin # Install Master Series (Project Management) openclawmp install skill/b42772e4cb38496096da58226657477c # Ding Shizhao openclawmp install skill/5f90e4007aec4faaa0728706a36219b6 # Ren Hong openclawmp install skill/e0a2d954385b48828d867affac429af6 # Ding Lieyun # Install Master Series (International Engineering) openclawmp install skill/82851afe1e50453b82bad3af859e5a48 # Zhang ShuiboThe comments above are translated into English for report-language compliance; the commands and asset identifiers are reproduced unchanged.
Technical Analysis
The Skill directs users to install externally hosted Skills through the
clawhubandopenclawmppackage ecosystems. The referenced packages are not included in the audited repository. Consequently, their source code, instruction content, permissions, manifests, and runtime behavior could not be reviewed.The installation commands do not pin a cryptographically verifiable artifact hash, provide a trusted source URL, identify a validated publisher key, or require inspection of the downloaded package before activation. Asset identifiers can identify remote packages, but they do not independently demonstrate integrity or publisher authenticity. If an external account, registry, package, or resolution mechanism is compromised, the installed content could differ from what the author intended.
This is a supply-chain exposure rather than evidence that any referenced package is currently malicious. ...[truncated 1333 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin every external Skill to an immutable, versioned artifact rather than a mutable package reference.
- Publish and verify a cryptographic digest, such as SHA-256, for each reviewed artifact.
- Document the verified publisher identity and use registry signature verification where supported.
- Link to auditable source code and record the source revision corresponding to each distributed artifact.
- Document the permissions, tools, network access, and filesystem access required by every dependency.
- Require users to download and inspect each Skill's manifest, instructions, and scripts before activation.
- Run third-party Skills in a sandbox with least-privilege filesystem, process, credential, and network access.
- Replace the generic
[assetId]placeholder with a documented, immutable, reviewed reference. - Avoid presenting direct installation as a one-step trusted operation; add an explicit verification stage before installation and activation.
- Maintain a dependency inventory and periodically re-audit referenced packages for ownership or content changes.
