T06 · System Persistence
- Location
SKILL.md:25- 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 clearly says it auto-updates Clawdbot and all skills, but that gives it broad recurring authority to change executable agent behavior without per-update review.
Install only if you are comfortable with Clawdbot and every installed skill being changed automatically on a schedule. Prefer a dry-run or notification-only setup, pin or allowlist trusted skills where possible, review updates before applying them, and know how to remove the cron job before enabling it.
SKILL.md:25Persistent Daily Update Task Executes Across Sessions
SKILL.md:43Unpinned Unattended Core and Skill Supply-Chain Updates
The script runs clawdhub update --all, which performs bulk self-modification of the agent's installed skills without human review. In this skill's context, that is especially risky because skills are executable agent capabilities; automatic updates can introduce malicious or unsafe behavior through a compromised publisher, dependency, or registry 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"
This skill explicitly sets up unattended daily updates for the core bot and all installed skills, which will modify executable software and skill files on a schedule. While the body explains what it does, the top-level description does not present a prominent warning about automatic scheduled changes, reducing informed consent and increasing the risk of unexpected supply-chain or stability issues if an update is malicious, compromised, or simply breaking.
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 set up unattended daily updates that will modify Clawdbot and all installed skills automatically, but it does not require an explicit user warning or renewed consent about ongoing software changes. This is dangerous because it enables recurring system and skill modifications, potentially pulling unreviewed code from upstream and changing runtime behavior without the user fully appreciating the trust and supply-chain risk.