T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:40- Finding
Unpinned Remote Payload Retrieval and Execution
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 40–43
Vulnerability Type: Remote payload retrieval and execution
Risk Level: Highbash git clone https://github.com/openclaw-skills/ai-intelligent-employee-onboarding cd ai-intelligent-employee-onboarding pip install -r requirements.txt python app.pyTechnical Analysis
The installation instructions retrieve a mutable external Git repository without pinning it to a reviewed commit or immutable release. They subsequently install dependencies from the retrieved
requirements.txtand execute the retrievedapp.py.The remote source code and dependency manifest are not included in the audited artifact, which contains only
SKILL.mdandskill.json. Consequently, the effective payload cannot be verified during this audit and may change after publication or review. Both Python package installation hooks andapp.pycan execute arbitrary code with the privileges of the user following these instructions.Package provenance is also unclear because
skill.jsonidentifies the author asyang1002378395-cmyk, whileSKILL.mdattributes the project to “OpenClaw Skills Team.” This discrepancy does not independently prove malicious behavior, but it limits confidence in the external repository's ownership.Attack Path
- An attacker compromises the referenced repository, gains control of its publishing account, or otherwise causes malicious content to be added to its default branch.
- The attacker modifies
app.py,requirements.txt, or a referenced dependency to include an arbitrary payload. - A user follows the documented installation procedure and clones the current default branch without an immutable revision pin.
pip install -r requirements.txtmay execute malicious package installation or build hooks.python app.pydirectly executes the remotely controlled application payload.- The payload operates with the invoking user ...[truncated 687 chars]
- Remediation
View remediation
Remediation Suggestions
- Include the complete, auditable application source and dependency manifests directly in the Skill package.
- If external retrieval is unavoidable, pin the repository to a reviewed full commit SHA rather than cloning a mutable default branch.
- Verify downloaded content using cryptographic hashes or signed releases before installation or execution.
- Pin every Python dependency to an exact reviewed version and require package hashes, such as through
pip install --require-hashes. - Generate and review a software bill of materials and use automated dependency vulnerability scanning.
- Publish verifiable repository ownership and reconcile the author discrepancy between
skill.jsonandSKILL.md. - Execute installation and startup in a least-privileged, isolated environment without unnecessary credentials, sensitive mounts, or host access.
- Replace direct execution instructions with a reproducible build process based on immutable, reviewed artifacts.
