T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:17- Finding
Execution of Mutable Python Code from a Remote URL
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is purpose-aligned, but it tells users to run mutable remote code and streams detailed agent content to VizClaw by default, so it needs careful review before installation.
Install only if you are comfortable sending OpenClaw run content to VizClaw. Prefer overview mode for normal use, avoid streaming secrets or private project data, do not run the remote uv URL unless you trust that live hosted script, and prefer pinned/reviewed local versions where available.
SKILL.md:17Execution of Mutable Python Code from a Remote URL
scripts/connect.py:1069Sensitive OpenClaw Content Is Transmitted to an External Service by Default
SKILL.md:9Unpinned Runtime and Installation Dependencies
The skill advertises executable commands that fetch and run remote code and stream agent events, but it does not declare an explicit tool scope such as network or file access permissions. That makes the capability boundary unclear to users and tooling, increasing the chance that the skill is installed or trusted without understanding that it can read local inputs and transmit data off-host.
Using 'npx clawhub@latest install vizclaw' relies on an unpinned, mutable package version, so future installs may execute different code than was originally reviewed. In a security-sensitive context, this creates a supply-chain risk: a compromised publisher, dependency, or registry response could cause arbitrary code execution during installation.
The OpenClaw gateway token is inserted into the WebSocket query string while also being sent as an Authorization header. Query-string credentials are commonly exposed through logs, proxies, browser/history-style telemetry, exception messages, and server access logs, increasing the chance of credential leakage beyond the intended recipient.
The script forwards queries, agent reports, tool usage, and other event content to remote VizClaw endpoints by default, but the CLI UX does not prominently warn users that potentially sensitive prompts, logs, and agent output will leave the local system. In this skill context, that matters because the tool is explicitly designed as a bridge for OpenClaw runs and log streams, which may contain secrets, internal code, or operational data.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
parser = argparse.ArgumentParser(description="VizClaw Connect")
parser.add_argument("--hub", default="wss://api.vizclaw.com/ws/report", help="WebSocket hub URL")
parser.add_argument("--api", default="https://api.vizclaw.com/api/report", help="HTTP API URL")
parser.add_argument("--model", default="opus", help="Model name")
parser.add_argument("--mode", default="detailed", help="detailed | overview | hidden")
parser.add_argument("--trigger-source", default="human", help="human | cron | heartbeat")
No suspicious patterns detected.