T06 · System Persistence
- Location
SKILL.md:21- Finding
Persistent System-Wide Services for Dashboard and Network Exposure
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a disclosed mission-control dashboard, but it asks to install persistent system services and remotely expose an agent-control interface with root-level service configuration and little security scoping.
Review carefully before installing. Only use this on a machine where you are comfortable running a persistent OpenClaw control dashboard, and do not enable Tailscale exposure until access controls, allowed users, authentication, logs, and uninstall/disable steps are clear. The localhost curl examples are not exfiltration evidence, but the persistent root-level proxy service and autonomous execution endpoints deserve administrator review.
SKILL.md:21Persistent System-Wide Services for Dashboard and Network Exposure
SKILL.md:143Tailscale Proxy Service Executes with Unnecessary Root Privileges
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
{
"id": "service",
"kind": "systemd",
"label": "Create Mission Control systemd service",
"path": "/etc/systemd/system/mission-control.service"
},
{
The documentation encourages exposing the dashboard via Tailscale and advertises webhook/HTTP automation, but provides no warning about authentication, sensitive data exposure, or the risk of remote triggering. Because this dashboard appears to control agents, messages, documents, and automation, remote exposure without explicit security guidance can lead users to deploy an internet-reachable control plane unsafely.
The skill describes polling and execution endpoints that can trigger autonomous operations, including executing tasks based on message content, but does not warn that these actions may cause real side effects. In a mission-control product, undocumented autonomous execution is especially dangerous because users may invoke endpoints or enable polling without understanding they can drive agents to act on external or queued input.
The skill instructs creation of a root-level Tailscale proxy service for a dashboard, which expands exposure beyond the stated local dashboard function and grants network publication capability under root. In the context of a mission-control interface with agent messaging, task execution, documents, and webhooks, externally exposing the service materially increases attack surface and the blast radius of any app flaw or misconfiguration.
The service is configured to run as root and invokes sudo in ExecStart to publish the dashboard via Tailscale. Running a network-exposed helper as root violates least-privilege principles and increases the consequences of command misuse, service compromise, or future modifications to the service definition.
[Service]
Type=simple
User=root
ExecStart=/usr/bin/sudo /usr/bin/tailscale serve 3000
Restart=always
[Install]
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Check if server is running
curl http://localhost:3000
# Restart server
sudo systemctl restart mission-control
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
sudo systemctl restart mission-control
### Tailscale not working
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
sudo systemctl restart mission-control
### Tailscale not working