ClawHub
Back to skill

Security audit

API-SPORTS

Security checks for vulnerabilities and agentic risk

Overview

The skill is mostly a coherent API-SPORTS connector, but its first-time setup tells the agent to run unverified remote installer scripts directly in a shell.

Review this skill before installing. Routine API-SPORTS reads through the oo CLI are aligned with the stated purpose, but do not let an agent run the documented curl|bash or irm|iex installer automatically; install the CLI only from a trusted source using a verifiable, versioned method and explicit approval.

A.I.G

Vulnerability Patterns
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • 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
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Findings (1)

T03 · Remote Payload Retrieval and Execution

Error
Location
SKILL.md:64
Finding

Unverified Remote Installer Download and Immediate Shell Execution

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, lines 64–73
Vulnerability Type: Remote payload retrieval and execution
Risk Level: Critical

The first-time setup instructions download mutable installation scripts from an external server and immediately execute the returned content:

markdown
- **`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
  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell
  ```

Technical Analysis

Both installation commands directly connect a network retrieval mechanism to a command interpreter:

  • On macOS and Linux, curl retrieves install.sh and pipes it directly into bash.
  • On Windows, Invoke-RestMethod retrieves install.ps1 and pipes it into Invoke-Expression.

The instructions do not pin a release version, verify a cryptographic signature or checksum, or save the scripts for inspection before execution. Consequently, the effective code can change after the Skill has been reviewed. HTTPS protects the connection in transit but does not mitigate compromise of the hosting server, deployment pipeline, vendor account, or other infrastructure controlling the response.

Installing the CLI may be relevant to first-time setup, but immediate execution of an unverified remote response exceeds the minimum behavior required to tell the user that the prerequisite is missing. It also extends beyond the Skill's declared runtime tool restriction, Bash(oo *), because the installer itself can invoke arbitrary commands and tools.

Attack Path

  1. An attempted API-SPORTS operation fails because the oo CLI is unavailable.
  2. The setup fallback directs the user or Agent to execute one of the documented installer commands.
  3. An attacker compromises or otherwise gains cont ...[truncated 1379 chars]
Remediation
View remediation

Remediation Suggestions

  1. Remove both direct execution patterns:
    • Do not pipe curl output into bash.
    • Do not pipe Invoke-RestMethod output into Invoke-Expression.
  2. Prefer a trusted operating-system package manager or a version-pinned release from the vendor's verifiable official repository.
  3. Download the installer to a local file without executing it automatically.
  4. Pin the installer to a specific immutable version and publish its expected SHA-256 or stronger cryptographic digest.
  5. Verify the digest or a trusted code-signing signature before execution, and abort on verification failure.
  6. Display the exact source, version, requested privileges, and verification result to the user.
  7. Require explicit user approval before executing the verified installer; do not let an authentication or command-not-found error silently trigger installation.
  8. Run installation with standard user privileges unless elevated access is demonstrably necessary, and document any requested elevation.
  9. After installation, verify that the resolved oo executable originates from the expected installation path and release.
  10. Keep installation outside the normal API query workflow so routine read operations remain constrained to the declared oo command interface.

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
Confidence
97% confidence
Finding

The skill instructs the agent to install software by piping a remotely fetched script directly into the shell (curl ... | bash). This creates a supply-chain and remote code execution risk: if the hosting domain, transport, installer, or upstream distribution is compromised, arbitrary code would run on the user's machine with the agent's privileges.

Content

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

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The description says to use this skill for "ANY API-SPORTS request" and "Whenever a task involves API-SPORTS, use this skill," which is a very broad activation condition. It does not provide boundaries, exclusions, or negative examples to clarify when the skill should not be invoked.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.