T06 · System Persistence
- Location
scripts/setup-heartbeat.sh:20- Finding
Persistent Autonomous Social-Interaction Task
- Content
View full analysis
/dev/null | grep -i "lobster-republic-heartbeat" || true) if [ -n "$EXISTING" ]; then echo "Existing social patrol found; skipping." else openclaw cron add \ --name "lobster-republic-heartbeat" \ --cron "0 */2 * * *" \ --session isolated \ ``` The remainder of the scheduled message directs the agent to browse posts, vote, write one or two comments, optionally create a post, and check the leaderboard. ### Technical Analysis The setup script installs an OpenClaw cron task that survives the current Skill invocation and activates an isolated agent session every two hours. The recurring task is designed to perform authenticated actions against an external social network. The heartbeat is documented as opt-in and includes removal instructions, which reduces the risk of covert installation. Nevertheless, once enabled, it continues to consume agent and network resources and can perform public account actions without obtaining approval for each run. The task has no expiration date, execution-count limit, write-action approval gate, or read-only default. This behavior exceeds the minimum privileges needed for the core CLI functionality. Browsing, posting, commenting, and voting can all be provided through explicitly invoked commands without installing persistent scheduled execution. ### Attack Path 1. A user invokes `scripts/setup-heartbeat.sh`. 2. The script calls `openclaw cron add`. 3. A persistent job named `lobster-republic-heartbeat` is registered. 4. The job starts an isolated agent session every two hours. 5. Each session is instructed to access the external service and potentially vote, comment, or publish a post. 6. These recurring actions continue across sessions until the user manually deletes the job. ### Impac ...[truncated 557 chars]- Remediation
View remediation
