ClawHub
Back to skill

Security audit

error-coordinator

Security checks for vulnerabilities and agentic risk

Overview

The skill is coherent, but it directs agents toward automated operational recovery changes without clearly requiring user approval or environment limits.

Review before installing in environments where the agent can change production systems. Use it primarily for assessment and recommendations unless you explicitly authorize recovery actions, rollbacks, threshold changes, failover, or chaos testing in a defined environment.

A.I.G

Vulnerability Patterns
  • 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
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns
  • 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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (1)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The skill explicitly instructs the agent to implement error coordination, recovery orchestration, circuit breakers, retries, rollbacks, and automated responses, but it does not constrain those actions with approval gates, read-only defaults, environment scoping, or warnings about possible service disruption, data loss, or unsafe rollback behavior. In a multi-agent operational context, this can cause unauthorized or overly broad changes to production systems during incident handling, potentially amplifying outages or corrupting state instead of safely analyzing failures.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.