ClawHub
Back to skill

Security audit

Docker Compose Optimizer

Security checks for vulnerabilities and agentic risk

Overview

This skill is a straightforward Docker Compose review guide with no hidden execution, persistence, or credential collection behavior found.

Install this skill when you want help reviewing Docker Compose files. Be aware that it may read compose files in the working directory during analysis, and invoke it with Compose-specific wording if you want to avoid accidental use on unrelated configuration reviews.

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
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · SKILL.md (reported line 90)May include surrounding context.

md
2. **Secrets in compose file** — DB password inline
   `POSTGRES_PASSWORD: mypassword123`
   → Move to .env file or Docker secrets

### 🟡 Improvements (4)
3. No memory limits on any service — risk of one service OOM-killing others

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The skill’s activation examples are broad and map to very common review requests, which can cause the skill to trigger in situations where a user may have intended a more general configuration review. Over-broad invocation boundaries increase the chance of unintended file access or execution of the skill’s analysis workflow on sensitive repositories or compose files.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.