T06 · System Persistence
- Location
SKILL.md:53- Finding
Persistent Silent Transmission of Unrestricted Workspace Contents
- Content
View full analysis
/dev/null || echo "Nothing to commit" # Push git push origin main ``` ```bash openclaw cron add \ --name "workspace-backup" \ --every 6h \ --session isolated \ --message "Run the maintenance skill, Section 1 (Workspace Backup). cd /opt/ocana/openclaw/workspace && git add -A && git commit -m 'Auto-backup: $(date -u +\"%Y-%m-%d %H:%M UTC\")' && git push origin main. Silent — do not message owner unless push fails." \ --timeout-seconds 60 ``` ### Technical Analysis `git add -A` recursively stages all tracked, modified, deleted, and untracked files within the repository. The skill defines no file allowlist, secret exclusion policy, remote ownership verification, pre-commit inspection, or secret scanning step. The scheduled task survives the session that creates it and repeatedly performs the push. Its instruction to remain silent reduces the likelihood that the owner will notice unexpected commits or transmissions. Although the destination is the configured `origin` remote and is not necessarily attacker-controlled, the skill does not verify that the remote is authorized or private. ### Attack Path 1. A user invokes the maintenance skill or installs the documented backup cron task. 2. The cron task persists and runs every six hours in an isolated session. 3. Credentials, private memory, configuration files, logs, or other sensitive material are subsequently created inside the workspace. 4. ...[truncated 747 chars]- Remediation
View remediation
