T06 · System Persistence
- Location
SKILL.md:29- Finding
Persistent Unattended Update Task Through Gateway Cron
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is an auto-updater as advertised, but it recommends a persistent unattended job that can update all skills, optionally update and restart Clawdbot, and send reports to a fixed Telegram recipient.
Review carefully before installing. Use this only if you intentionally want unattended updates, replace the Telegram recipient and hard-coded paths with your own verified values, prefer report-only checks or explicit approvals, and keep rollback/provenance checks for skill and Clawdbot updates.
SKILL.md:29Persistent Unattended Update Task Through Gateway Cron
SKILL.md:29Update and Diagnostic Reports Sent to a Hard-Coded Telegram Recipient
SKILL.md:14Machine-Specific Executable and Workspace Paths Used in Setup Commands
This skill instructs the scheduler to run clawdhub update --all automatically and optionally apply a Clawdbot update and restart. That is a real self-modification capability: it changes the local software and installed skills based on remote content, and when placed in an unattended cron job it increases supply-chain and integrity risk if a package, skill, account, or update channel is compromised.
--deliver
--channel telegram
--to "2095290688"
--message "Run daily auto-update: update skills via clawdhub update --all; if Clawdbot has an update available, apply it and restart; then run clawdbot doctor --non-interactive; report what changed."
## What the job should do (workflow)
The explicit workflow step clawdhub update --all causes unattended modification of all installed skills. Even though the feature is presented as maintenance automation, it is still a genuine risky pattern because it can pull and execute changed skill content without human review, magnifying the blast radius of a compromised upstream dependency or account.
- `clawdbot --version`
- `clawdhub list` (skills + versions)
2) Update skills
- `clawdhub update --all`
3) (Optional) Update Clawdbot
The skill recommends optional Clawdbot self-updates followed by health checks and restart, which is direct self-modification of the running agent environment. This is especially sensitive because it can replace the bot binary/runtime and immediately restart into new code during an unattended job, reducing opportunities for review and potentially enabling persistent compromise if the update source is tampered with.
- `clawdhub update --all`
3) (Optional) Update Clawdbot
- Only if the owner explicitly wants self-updates.
- After updating, run `clawdbot doctor --non-interactive`.
- Restart gateway if required.
This note reinforces automated Clawdbot self-update behavior and frames restarts as an operational concern rather than a security-sensitive code change. In context, it normalizes unattended self-modification, which is dangerous because scheduled background execution makes malicious or faulty updates harder to notice promptly, though this line itself is less actionable than the earlier explicit commands.
- **Timezone field:** in Gateway job objects this is `schedule.tz` (IANA tz like `Europe/Stockholm`).
- **Delivery:** Prefer explicit `channel` + `to` so the job always reaches you.
- **Clawdbot self-update:** can be disruptive (restarts). Run at a quiet time.
## Troubleshooting
No suspicious patterns detected.