Back to skill

Security audit

WaiverFile

Security checks for vulnerabilities and agentic risk

Overview

This WaiverFile skill is mostly coherent, but it needs review because it can read connected waiver data and includes an unverified remote installer command.

Review before installing. Use this only where reading WaiverFile records through an OOMOL-connected account is intended. Prefer installing the oo CLI through a verified package or inspected installer rather than directly piping the remote install script into a shell.

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 users to install software via `curl -fsSL https://cli.oomol.com/install.sh | bash`, which executes a remote script directly without prior inspection or integrity verification. If the host, transport, or script supply chain is compromised, this becomes arbitrary code execution on the user's machine; the skill context makes this more dangerous because it is presented as an operational recovery step inside a trusted workflow.

Vague Triggers

Medium
Confidence
95% confidence
Finding
The trigger description is excessively broad: "Use this skill for ANY WaiverFile request" and "Whenever a task involves WaiverFile, use this skill instead of calling the API directly." This can cause the agent to invoke the skill for loosely related mentions of WaiverFile, increasing the chance of unnecessary data access or execution in contexts where the user did not explicitly intend tool use.

Static analysis

No suspicious patterns detected.