T06 · System Persistence
- Location
references/agent-guide.md:76- Finding
Persistent Daily Update Task Executes Across Sessions
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill openly sets up automatic updates, but it should be reviewed because it creates a persistent daily job that can change Clawdbot and every installed skill without fresh approval each time.
Install only if you intentionally want unattended daily updates to Clawdbot and every installed skill. Prefer running a dry run first, limiting updates to trusted skills or approved versions, using a least-privileged account, and confirming you know how to inspect and remove the cron job.
references/agent-guide.md:76Persistent Daily Update Task Executes Across Sessions
references/agent-guide.md:41Unattended Installation of Mutable Latest Packages and Skill Updates
references/agent-guide.md:54Critical Update and Migration Failures Are Suppressed
The skill explicitly performs clawdhub update --all, which is direct self-modification of the agent's installed skill set. This is dangerous because it grants scheduled, unattended authority to replace or alter agent capabilities, creating a strong supply-chain compromise path and increasing the blast radius of a malicious or broken skill update.
# 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 sets up unattended recurring updates that will modify the Clawdbot installation and all installed skills, but the user-facing description does not prominently warn that software and skill files will be changed automatically on a schedule. This can lead to users enabling persistent self-modification without fully understanding the trust and supply-chain implications, especially because clawdhub update --all pulls and applies remote changes across all skills.
The guide instructs the agent to perform unattended updates to the core bot and all installed skills, which can change code, behavior, dependencies, and configuration without any explicit warning, approval gate, or rollback guidance. In an agent context, automatic self-updating materially increases supply-chain and operational risk because compromised packages or breaking changes can be applied silently on a schedule.
The guide recommends creating a persistent helper script under ~/.clawdbot/scripts/auto-update.sh, which establishes durable executable state that can be reused by future runs. In combination with cron-based execution and update authority, this persistence increases risk because any later tampering with that script can repeatedly execute under the user's automation flow.
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 customization example allows delivery of update summaries to external providers such as Telegram, but it does not warn that logs or update results may contain sensitive operational details, package names, errors, paths, or other metadata. This can unintentionally disclose environment information to third-party services or recipients if misconfigured.
The setup confirmation example states that daily updates will run at 4:00 AM in America/Los_Angeles. This natural-language example enforces a specific locale/time zone and does not indicate user opt-in, configurability, or a region-specific requirement.