Back to skill

Security audit

model-troubleshooter

Security checks for vulnerabilities and agentic risk

Overview

This troubleshooting skill has a coherent purpose, but it asks to automatically read broad configuration/log data, modify model settings, restart services, and add persistent monitoring without clear user approval.

Install only if you are comfortable with an agent inspecting broad OpenClaw configuration and logs and potentially changing model defaults, restarting the gateway, and creating persistent monitoring or memory notes. A safer version should run read-only by default, ask before reading sensitive logs, show redacted diffs before every config change, require confirmation before restarts or provider switches, and make any memory or heartbeat behavior opt-in and removable.

Vulnerability Patterns
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
  • System PersistenceInstalls backdoors, hooks, services, or scheduled tasks that survive the run
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
Findings (4)

T02 Β· Agent Memory Poisoning

Error
Location
skill.md:190
Finding

Persistent Agent Behavior Written to Long-Term Memory

Content
View full analysis
Remediation
View remediation

T06 Β· System Persistence

Error
Location
skill.md:190
Finding

Automatic Installation of Recurring Health Checks and Cross-Session Rules

Content
View full analysis
Remediation
View remediation

T05 Β· Unauthorized Access and Privilege Escalation

Error
Location
skill.md:21
Finding

Overbroad Collection of Sensitive Configuration and Gateway Logs

Content
View full analysis
Remediation
View remediation

T09 Β· Insecure Skill Coding Practices

Error
Location
skill.md:6
Finding

Unsafe Automatic Configuration Mutation and Gateway Restart

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Findings (6)

Vague Triggers

High
Category
Not specified by scanner
Confidence
98% confidence
Finding

The trigger 'Any model-related complaint' is overly broad and can activate the skill in many normal conversations, causing sensitive diagnostic actions to run when the user did not specifically request them. In this skill, auto-activation is especially risky because activation can lead to config inspection, log access, and follow-on system changes.

Content

No source excerpt is available for this finding.

Missing User Warnings

High
Category
Not specified by scanner
Confidence
98% confidence
Finding

The skill authorizes automatic config patches, gateway restarts, and file updates without an upfront warning or explicit consent gate. These are system-impacting operations that can interrupt service, modify persistent state, and create unintended outages or misconfigurations if triggered automatically.

Content

No source excerpt is available for this finding.

Ssd 3

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

Persisting troubleshooting details in MEMORY.md risks storing provider names, failure history, endpoint details, and possibly fragments of sensitive configuration beyond the immediate session. Long-lived memory increases exposure surface and can leak operational or secret-adjacent information to later tasks or users.

Content

No source excerpt is available for this finding.

Autonomous Decision Making

Medium
Category
Excessive Agency
Confidence
90% confidence
Finding

The skill permits autonomous decision-making for provider switching when it deems the error 'critical,' without a strong, objective boundary or mandatory human approval. In context, this autonomy combines with config patching and restart capabilities, creating real risk of unauthorized or harmful environmental changes.

Content

Scanner excerpt Β· skill.md (reported line 285)May include surrounding context.

md
1. **Never guess** β€” always scan config first
2. **Never apply temporary fix** β€” only permanent solutions
3. **Never switch without confirmation** β€” unless critical error blocking all work
4. **Always verify** β€” test after every fix
5. **Always educate** β€” tell user WHAT broke and WHY it won't break again
6. **Always backup** β€” note what changed in MEMORY.md

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The skill contains conflicting instructions: it claims it will never switch providers without confirmation, but earlier sections authorize automatic provider migration as a permanent fix. Conflicting autonomy rules are dangerous because the more aggressive branch may be followed during failure handling, leading to unapproved configuration changes that alter user service behavior.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
83% confidence
Finding

The skill promises not to expose secrets, yet it directs automatic reading of full configuration and provider data, which commonly includes sensitive metadata and may include credentials or enough context to leak them in logs, summaries, or persisted notes. In a troubleshooting skill that auto-runs and generates reports, this contradiction increases the chance of accidental secret disclosure even if the author intended redaction.

Content

No source excerpt is available for this finding.