ClawHub
Back to skill

Security audit

Supabase

Security checks for vulnerabilities and agentic risk

Overview

This is a coherent Supabase connector skill, but it includes risky one-time setup commands and can operate on sensitive Supabase resources.

Install only if you trust OOMOL and are comfortable granting connector access to your Supabase account. Avoid letting an agent run the provided installer pipe commands automatically; install the oo CLI manually from a trusted source and verify it first. Review each write or destructive Supabase action carefully before approval.

SkillSpector

Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • 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
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (2)

External Script Fetching

High
Category
Supply Chain
Content
- **`oo: command not found`** — install the oo CLI (other platforms: <https://cli.oomol.com/install-guide.md>):

  ```bash
  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux
  ```

  ```powershell
Confidence
97% confidence
Finding
The skill instructs the agent to install software using a remote script piped directly into a shell (`curl ... | bash`), which is a classic unsafe pattern. If the remote host, transport, or script content is compromised, this can lead to arbitrary code execution on the agent host; in this skill context, the risk is heightened because the command appears in operational setup guidance that an agent may follow automatically after an error.

Vague Triggers

Medium
Confidence
95% confidence
Finding
The manifest description says to use this skill for "ANY Supabase request" and "Whenever a task involves Supabase," which is a very broad activation condition without constraints or negative examples. This can overlap with many ordinary references to Supabase and does not clearly define when the skill should not activate.

Static analysis

No suspicious patterns detected.