Back to skill

Security audit

Auto Updater.Bak2

Security checks for vulnerabilities and agentic risk

Overview

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.

Vulnerability Patterns
  • System PersistenceInstalls backdoors, hooks, services, or scheduled tasks that survive the run
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
Findings (2)

T06 · System Persistence

Error
Location
SKILL.md:25
Finding

Persistent Daily Update Task Executes Across Sessions

Content
View full analysis
Remediation
View remediation

T08 · Insecure Dependencies

Error
Location
SKILL.md:43
Finding

Unpinned Unattended Core and Skill Supply-Chain Updates

Content
View full analysis
&1 | tee -a "$LOG_FILE" || true ``` ### Technical Analysis The update workflow resolves the mutable `latest` package target and updates every installed Skill without specifying approved versions, cryptographic hashes, signatures, or trusted release identities. There is no documented staging, source review, integrity verification, or user confirmation before installation. Package-manager updates may execute installation lifecycle behavior, while Skill updates may introduce new scripts or agent instructions. Running `clawdbot doctor --yes` also applies migrations non-interactively. Consequently, the effective code and instruction payload can change after this Skill has been reviewed. The helper script suppresses certain failures with `|| true`, including failures from the source update, doctor operation, and Skill update capture. This can allow the routine to continue after a partial or unsuccessful update, increasing the possibility of inconsistent runtime state and reducing the reliability of failure enforcement. ### Attack Path 1. An attacker compromises an upstream publisher account, package registry entry, release pipeline, or Skill publisher. 2. The attacker publishes a malicious release under the expected Clawdbot package or an already installed Skill. 3. The daily update task resolves `clawdbot@latest` or executes `clawdhub update --all`. 4. Because no approved-version policy, signature check, hash check, ...[truncated 1265 chars]
Remediation
View remediation
Vulnerability Patterns
  • Rogue AgentSelf-Modification, Session Persistence
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (4)

Self-Modification

High
Category
Rogue Agent
Confidence
98% confidence
Finding

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.

Content

Scanner excerpt · references/agent-guide.md (reported line 61)May include surrounding context.

md
# 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"

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Session Persistence

Medium
Category
Rogue Agent
Confidence
60% confidence
Finding

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.

Content

Scanner excerpt · references/agent-guide.md (reported line 21)May include surrounding context.

bun pm ls -g 2>/dev/null | grep clawdbot && echo "bun-global"

text

## Step 2: Create the Update Script (Optional)

For complex setups, create a helper script at `~/.clawdbot/scripts/auto-update.sh`:

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

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.

Content

No source excerpt is available for this finding.