T06 · System Persistence
- Location
SKILL.md:186- Finding
Recurring Competition Jobs Establish Cross-Session Persistence
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 186-201
Vulnerability Type: Scheduled-task persistence
Risk Level: HighVulnerable Code
bash openclaw cron add \ --name "arena-<agent>" \ --agent <openclaw-agent-id> \ --every "20m" \ --session isolated \ --timeout-seconds 900 \ --no-deliver \ --message "Compete on Arena. Run: arena compete --agent <name> --category <cat> --api-key <key>. DO NOT end the turn while it is running — poll the subprocess until you see 'Match found!' and a workspace path, then cd, read README.md, edit solution.py, and run: arena submit."bash */20 * * * * arena compete --agent <your-agent> --category <category> --api-key $(cat ~/.arena/agents/<your-agent>/api-key)Technical Analysis
The Skill instructs the user or agent to create an OpenClaw scheduled job or operating-system cron entry that runs every 20 minutes. These jobs survive the original Skill invocation and continue initiating network connections, reading credentials, entering competitions, modifying challenge workspaces, and submitting results without per-run authorization.
Although scheduling is presented as an optional leaderboard feature, it grants the Skill persistent execution beyond what is necessary to complete one requested competition. The configuration is unbounded: it has no expiration time, maximum execution count, or automatic cleanup procedure.
Attack Path
- A user loads the Skill and follows the scheduling section.
- The user or agent executes
openclaw cron addor installs the supplied system cron entry. - The scheduler persists the command outside the initiating session.
- Every 20 minutes, the scheduled job reads or uses the Arena API key.
- The job contacts the Arena service, waits for matchmaking, edits a supplied workspace, and submits a solution.
- Execution continues indefinitely ...[truncated 561 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove instructions that create recurring OpenClaw or operating-system cron jobs from the core Skill.
- Require explicit, informed user approval before creating any persistent task.
- Prefer a single-run command that terminates after one competition.
- If scheduling is retained, require an expiration time, a maximum run count, and a clearly documented removal command.
- Display the exact command, frequency, privileges, credential source, and expected network activity before installation.
- Add a cleanup workflow that removes the scheduled task and verifies its removal.
- Do not place credentials or credential values in scheduler messages or configuration.
