Back to skill

Security audit

Coolify

Security checks for vulnerabilities and agentic risk

Overview

Coolify operations have approval safeguards, but setup directs the agent to run remote installation code without separate approval.

Review the setup before installing. Install a reviewed CLI release yourself, restrict the Coolify API key to necessary resources, and retain confirmation for deployments and destructive operations. The publisher documents OO_SKILLS_SYNC_DISABLED as a control for automatic skill synchronization. Remote installer contents and hosted connector behavior remain unverified.

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
Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Output HandlingUnvalidated Output Injection, Cross-Context Output, Unbounded Output
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Findings (4)

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

The supplied command executes a remote installer associated with Oomol, not Coolify. Nothing in the chunk establishes that this installation supports Coolify operations, so it represents a materially different purpose and an inconsistent external resource. The installer contents are not supplied, so its additional effects cannot be determined.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
98% confidence
Finding

The command pipes a mutable remote script directly into Bash, giving whatever the endpoint returns the privileges of the invoking account without prior verification. HTTPS protects transport but does not protect against compromise of the publisher or distribution infrastructure; the documented OOMOL dependency explains the domain but does not remove this supply-chain risk.

Content

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

The setup workflow executes downloaded installer scripts without warning the user about running remote code.

Medium
Category
Output Handling
Confidence
95% confidence
Finding

The fallback setup directs the agent to execute downloaded shell or PowerShell code without explicit installation approval, review, or integrity verification. Although this is a legitimate dependency setup path and only runs when the CLI is missing, it crosses from Coolify management into local code execution; a compromised installer could access files and credentials available to the agent's account.

Content

No source excerpt is available for this finding.

Autonomous Decision Making

Medium
Category
Excessive Agency
Confidence
80% confidence
Finding

Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Content

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

md
- **`OOMOL_INSUFFICIENT_CREDIT`** — OOMOL billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.

- **HTTP 402 without `OOMOL_INSUFFICIENT_CREDIT`** — the third-party account itself has no active plan or credit. Report the provider error message as is; do not ask the user to recharge OOMOL.

## Resources