T03 · Remote Payload Retrieval and Execution
- Location
README.md:96- Finding
Mutable Remote Executable Installed into the User PATH
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 96-103
Vulnerability Type: Mutable remote payload retrieval and execution
Risk Level: Mediumbash # Clone the skill git clone https://github.com/hopyky/self-reflection.git ~/.openclaw/skills/self-reflection # Add to PATH ln -sf ~/.openclaw/skills/self-reflection/bin/self-reflection ~/bin/self-reflection # Create config cp ~/.openclaw/skills/self-reflection/self-reflection.example.json ~/.openclaw/self-reflection.jsonTechnical Analysis
The documented installation procedure clones the mutable default branch of a remote Git repository without pinning a reviewed commit, verifying a cryptographic checksum, or validating a release signature. It then symlinks the remotely obtained
bin/self-reflectionexecutable into the user's~/bindirectory.Consequently, the code users install may differ from the code that was reviewed. The executable referenced by these instructions is also absent from the submitted artifact, preventing verification of its behavior. The exposure is amplified by the documented heartbeat integration, which instructs the agent to invoke
self-reflection checkperiodically.No evidence establishes that the current upstream repository is malicious. The vulnerability is the mutable and unverified remote-code installation mechanism.
Attack Path
- An attacker compromises the upstream repository, its maintainer account, or another mechanism capable of modifying its default branch.
- The attacker adds malicious commands to
bin/self-reflection. - A user follows the README and clones the mutable default branch without integrity verification.
- The installation procedure symlinks the downloaded executable into
~/bin. - The user or configured OpenClaw heartbeat invokes
self-reflection check. - The malicious commands execute with the privileges of the affected user.
Impact Assessment
Successful expl ...[truncated 475 chars]
- Remediation
View remediation
Remediation Suggestions
- Distribute the executable inside the reviewed skill artifact so the installed implementation matches the audited content.
- Pin installation to an immutable, reviewed Git commit or versioned release rather than the repository's default branch.
- Publish and verify a SHA-256 or stronger digest before installation.
- Sign releases and require signature verification against a documented maintainer key.
- Avoid symlinking unverified remote content directly into a PATH directory.
- Ensure automated heartbeat execution begins only after package integrity and executable contents have been validated.
- Add the missing executable implementation to future audit submissions so its command parsing, file operations, and trust boundaries can be reviewed.
