T08 · Insecure Dependencies
- Location
SKILL.md:45- Finding
Unpinned Remote Packages and Skills Are Installed and Executed
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:45-57, 72-95, 119-150, 201-218
Vulnerability Type: Unpinned third-party dependencies and mutable remote updates
Risk Level: MediumEvidence
bash npm i -g openclawbash npm i -g clawhub clawhub loginbash openclaw skills install obsidian-memory-system openclaw skills install soft-ip-full-lifecycle-zijian openclaw skills install database-specialist openclaw skills install cross-platform-memory-hub openclaw skills install soft-ip-full-lifecycle-delivery-pro openclaw skills install ssq-analyzerbash openclaw skills install clawtipbash python3 scripts/create_order.py "read permanent memory" python3 scripts/service.py "20260716123456123456"bash openclaw skills update --allTechnical Analysis
The guide instructs users to install npm packages and OpenClaw Skills without specifying immutable versions, package integrity hashes, trusted publisher fingerprints, or verified artifact references. It subsequently directs the agent to execute Python scripts supplied by those remotely installed Skills.
The mandatory
clawtippayment component is especially sensitive because the documented workflow grants it access to local order files, payment state, filesystem writes, and an external payment API. Its implementation is not included in the audited project and therefore cannot be independently reviewed here.The
update --allcommand further permits reviewed components to be replaced with newer remote versions without per-component review. A compromised registry account, publisher account, dependency, or Skill release could therefore introduce arbitrary code after this guide itself has passed review.Attack Path
- An attacker compromises a referenced npm or ClawHub publisher, dependency, or release channel.
- The attacker publishes a malicious version under an existing referenc ...[truncated 1118 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin every npm package and OpenClaw Skill to an exact, reviewed version.
- Provide cryptographic integrity hashes or signed, immutable artifact references.
- Document the official registry, package namespace, publisher identity, and signing fingerprint for each dependency.
- Avoid global npm installation where possible; use an isolated, least-privileged environment.
- Vendor or otherwise expose the source of security-sensitive components such as
clawtipfor review. - Require explicit user approval before installing or updating executable components.
- Replace
openclaw skills update --allwith explicit, version-specific updates reviewed before installation. - Execute third-party Skills inside a sandbox with narrowly scoped filesystem and network access.
- Verify package signatures and integrity before invoking any installed script.
