Umbrel Proxy Manager

Efficiently manage and interact with Umbrel proxy services for Docker containers. Automatically discovers running services, maps internal Docker IPs to acces...

This skill appears to do what it says, but review and exercise standard caution before running: 1) Inspect the scripts (they are bundled) — they call docker, openclaw, curl/requests and write umbrel_services.json/connectivity results. 2) Run discovery and use update scripts with --dry-run first (update_openclaw_config.py supports dry-run) to see planned changes. 3) Backup your OpenClaw config (~/.openclaw/openclaw.json or your system path) before allowing automatic updates. 4) Run as a local admin user; avoid running in environments where container names or the mapping JSON could be attacker-controlled (the scripts use shell execution and have limited input sanitization). 5) Ensure Docker and OpenClaw binaries are trusted and on your system PATH. If you want higher assurance, run the discovery scripts only, inspect umbrel_services.json, then run updates manually.

Type: OpenClaw Skill Name: umbrel-proxy Version: 1.0.3 The skill automates Umbrel and OpenClaw integration by discovering Docker containers and updating configurations. It exhibits high-risk behavior by executing shell commands via subprocess.run(shell=True) in discover_umbrel_services.py and update_openclaw_config.py, creating a shell injection vulnerability where container names or configuration values are used to construct commands. While the intent appears benign and aligned with the documentation, the combination of broad system access (Docker) and insecure coding practices warrants a suspicious classification.