T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:45- Finding
Mutable Remote Payload Retrieved and Executed Without Integrity Verification
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 45–48
Vulnerability Type: Remote payload retrieval and execution
Risk Level: HighVulnerable Code:
bash git clone https://github.com/openclaw-skills/ai-intelligent-ar-vr-platform cd ai-intelligent-ar-vr-platform pip install -r requirements.txt python app.pyTechnical Analysis
The installation instructions clone a mutable external Git repository without pinning a reviewed commit, validating a cryptographic checksum, or verifying a trusted signature. They subsequently install dependencies from an unaudited
requirements.txtfile and execute the downloadedapp.py.The audited package contains neither the referenced application nor its dependency manifest. Consequently, the effective code executed by users can differ from the code available when this skill was reviewed. Although unsafe dependencies are also part of the exposure, the best matching classification is remote payload retrieval and execution because the instructions explicitly download and run an externally controlled application.
Python package installation can execute package build or installation hooks before
app.pyis launched. Therefore, malicious code could run during eitherpip installorpython app.py.Attack Path
- An attacker compromises the referenced repository, its maintainer account, or an upstream dependency source.
- The attacker modifies the repository's default branch,
requirements.txt, orapp.pyto include a malicious payload. - A user follows the documented installation commands.
git cloneretrieves the attacker-controlled, mutable content without integrity validation.pip install -r requirements.txtmay execute malicious package build hooks or install compromised dependencies.python app.pydirectly executes the downloaded application.- The payload operates with the permissions of the user who ran the commands.
...[truncated 683 chars]
- Remediation
View remediation
Remediation Suggestions
- Include the complete application source and dependency manifests inside the auditable skill package.
- If remote retrieval is unavoidable, pin the repository to an immutable, reviewed commit hash rather than cloning and executing the default branch.
- Verify downloaded content using a trusted cryptographic signature or a securely distributed SHA-256 digest before installation or execution.
- Replace unconstrained dependencies with a reviewed lockfile containing exact versions and cryptographic hashes, such as a hash-locked requirements file used with
pip install --require-hashes. - Review direct and transitive dependencies for provenance, typosquatting, known vulnerabilities, and unexpected build hooks.
- Run the application in an isolated virtual environment or sandbox with minimal filesystem, network, credential, and operating-system permissions.
- Document the application's required permissions and explicitly instruct users not to run installation or execution commands as an administrator or root user.
- Perform security review and automated scanning on the exact pinned application revision before publication.
