T06 · System Persistence
- Location
SKILL.md:27- Finding
Persistent Unattended Auto-Update Task
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is an auto-updater, but it schedules unattended changes to Clawdbot and every installed skill, so users should review it carefully before enabling it.
Install only if you intentionally want unattended updates to Clawdbot and every installed skill. Prefer a dry-run or notify-only schedule, require approval before applying updates, pin or review versions where possible, run it under a low-privilege account, keep backups, and adjust the timezone before enabling the cron job.
SKILL.md:27Persistent Unattended Auto-Update Task
SKILL.md:51Automatic Retrieval and Installation of Mutable Remote Code
The script performs clawdhub update --all, which is direct self-modification of the agent's skillset from an external source without review. This is dangerous because it expands the agent's capabilities and behavior over time based on upstream content, creating a supply-chain and persistence risk if a skill is compromised, malicious, or simply incompatible.
# Capture new version
CLAWDBOT_VERSION_AFTER=$(clawdbot --version 2>/dev/null || echo "unknown")
# Update skills
log "Updating skills via ClawdHub..."
SKILL_OUTPUT=$(clawdhub update --all 2>&1) || true
echo "$SKILL_OUTPUT" >> "$LOG_FILE"
The skill explicitly sets up unattended daily updates that modify Clawdbot and all installed skills, but it does not present a prominent warning that software will be changed automatically on a schedule and without per-update confirmation. Automatic modification of installed software increases supply-chain and stability risk because newly published packages or skills are applied without user review, potentially introducing malicious or breaking changes.
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.
bun pm ls -g 2>/dev/null | grep clawdbot && echo "bun-global"
## Step 2: Create the Update Script (Optional)
For complex setups, create a helper script at `~/.clawdbot/scripts/auto-update.sh`:
The guide instructs the agent to perform unattended package and skill updates, run migration/repair commands, and deliver the results, but it does not require an explicit user warning, approval, rollback plan, or staging check before making system changes. This is dangerous because automatic updates can break the bot, alter behavior, or introduce malicious upstream changes, and the cron-delivered workflow normalizes repeated autonomous modification of the environment.
The example cron command hard-codes the timezone to America/Los_Angeles, which can cause the updater to run at an unexpected local time if copied verbatim by users outside that locale. In a skill that performs unattended software updates, unexpected execution timing makes the behavior less predictable and can increase operational risk, such as updates occurring during active usage or maintenance windows.
Line L086 specifies that daily updates will run at 4:00 AM in the America/Los_Angeles timezone. Under the policy, locale constraints should either be user-selectable or clearly justified; this example presents a fixed locale without that context.