T08 · Insecure Dependencies
- Location
README.md:15- Finding
Unpinned Remote Repository Installation
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 15-17
Vulnerability Type: Unpinned supply-chain dependency
Risk Level: MediumVulnerable Code
bash git clone https://github.com/spikesubingrui-design/venus-tracker.git ~/.openclaw/workspace/skills/venus-trackerTechnical Analysis
The installation instructions clone the current default branch of a remote Git repository without selecting an immutable commit or verifying a signature or checksum. Consequently, the content installed by this command can differ from the version covered by this audit.
Although the repository URL corresponds to the homepage declared by the Skill, this alone does not guarantee content integrity. A compromised maintainer account, repository, or upstream branch could modify the Skill instructions or introduce executable files after review.
Attack Path
- An attacker compromises the upstream repository or an authorized maintainer account.
- The attacker modifies the default branch to include malicious Skill instructions or executable content.
- A user follows the documented unpinned
git cloneinstallation command. - OpenClaw or another agent loads the modified Skill.
- The malicious content operates with the tools and permissions granted to the agent, including the Skill's declared shell capability.
Impact Assessment
Exploitation requires control of, or unauthorized write access to, the upstream repository. Successful exploitation could alter agent behavior or execute commands with the privileges of the user running the agent. The resulting scope could include accessible workspace files, agent-readable credentials, and external services available to the agent.
- Remediation
View remediation
Remediation Suggestions
- Pin installation to a reviewed, immutable Git commit or signed release tag.
- Publish and verify a SHA-256 checksum for release artifacts.
- Require signed commits or release signatures and document signature verification.
- Avoid automatically updating the installed Skill from a mutable branch.
- Re-audit the package whenever the pinned revision changes.
- Prefer a package installation mechanism with lockfiles, integrity metadata, and provenance verification.
