T03 · Remote Payload Retrieval and Execution
- Location
skill.md:44- Finding
Execution of Unpinned Code Retrieved from a Mutable Remote Repository
- Content
View full analysis
Vulnerability Details
File Location:
skill.md:44-47; duplicated installation workflow inREADME.md:127-130andREADME.md:146-164
Vulnerability Type: Remote payload retrieval and execution
Risk Level: HighVulnerable code snippet from
skill.md:44-47:text 1. Clone `https://github.com/compound-life-ai/longClaw`. 2. Change into the repository. 3. Run `python3 scripts/install_bundle.py`. 4. Run `python3 scripts/install_bundle.py --verify`.Corresponding code snippet from
README.md:127-130:text 1. Clone `https://github.com/compound-life-ai/longClaw` to a stable local path. 2. Change into the cloned repository. 3. Run `python3 scripts/install_bundle.py`. 4. Run `python3 scripts/install_bundle.py --verify`.Additional executable installation commands from
README.md:146-164:bash python3 scripts/install_bundle.py --dry-runbash python3 scripts/install_bundle.pybash python3 scripts/install_bundle.py --openclaw-home /path/to/.openclawbash python3 scripts/install_bundle.py --verifyTechnical Analysis
The skill directs an agent or user to clone an external GitHub repository and immediately execute its Python installer. The repository reference is not pinned to an immutable commit hash or signed release, and the instructions do not require verification of a cryptographic checksum or signature.
Consequently, the effective executable payload can change after this skill has been reviewed. The audited artifact contains only
skill.mdandREADME.md; it does not containscripts/install_bundle.py, the advertisedskills/directory, or the other executable components. Their implementation and safety therefore cannot be verified from the submitted project.The README states that the external installer copies scripts and skills, initializes runtime storage, and modifies
~/.openclaw/openclaw.jsonby registering ...[truncated 1920 chars]- Remediation
View remediation
Remediation Suggestions
- Include
scripts/install_bundle.py, all sub-skills, and every executable dependency directly in the reviewed artifact so installation behavior can be audited. - Pin remote installation to an immutable Git commit or versioned release instead of cloning the mutable default branch.
- Publish a SHA-256 checksum for the complete release artifact and require checksum verification before execution.
- Prefer cryptographically signed releases and verify the signature against a documented maintainer key.
- Display all proposed filesystem and configuration changes before applying them, and require explicit user approval.
- Execute installation with least privilege. Do not request administrator or root access when changes are limited to the user's OpenClaw directory.
- Validate copied paths and reject symbolic links, path traversal, or destinations outside the intended bundle directory.
- Back up
~/.openclaw/openclaw.jsonbefore modification and update it atomically. - Audit the pinned installer and every registered skill before instructing the user to start a fresh OpenClaw session.
- Update the documentation to use a workflow such as downloading a signed release, verifying its signature and checksum, inspecting the installation plan, and only then running the installer.
- Include
