Back to skill

Security audit

Streamtime

Security checks for vulnerabilities and agentic risk

Overview

The skill is a coherent Streamtime integration, but its setup instructions tell users to execute unverified remote installer scripts, which warrants Review before installation.

Review the install path before using this skill. Prefer an official signed or checksum-verified oo CLI installer, or download and inspect the installer before executing it. Only connect the Streamtime account you intend OOMOL to operate, and confirm any create or update payload before allowing write actions.

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 (2)

T03 · Remote Payload Retrieval and Execution

Error
Location
SKILL.md:68
Finding

Unverified Remote Shell Script Execution on macOS and Linux

Content
View full analysis

Vulnerability Details

File Location: SKILL.md:68
Vulnerability Type: Remote payload retrieval and immediate shell execution
Risk Level: High

Complete Code Snippet:

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

Technical Analysis

The installation instruction pipes a remotely downloaded script directly into bash. The payload is retrieved from a mutable URL without a pinned version, cryptographic signature verification, checksum validation, or an opportunity to inspect the downloaded file before execution.

HTTPS protects the connection in transit but does not guarantee that the server, deployment pipeline, domain, or current script contents are trustworthy. Because the effective payload can change after the Skill has been reviewed, compromise of the remote endpoint or its publishing infrastructure could turn this instruction into arbitrary code execution.

Installing the CLI may be relevant to the declared Streamtime connector functionality, but direct execution of an unverified remote script exceeds the minimum privileges and trust required to provide installation guidance.

Attack Path

  1. The oo CLI is unavailable and an action fails with oo: command not found.
  2. The agent or user follows the documented first-time setup instruction.
  3. curl retrieves the current contents of https://cli.oomol.com/install.sh.
  4. The pipe sends those contents directly to bash without local verification.
  5. A compromised or malicious remote payload executes with the permissions of the invoking account.
  6. The payload can perform any operation available to that account, including reading accessible data, modifying files, installing additional software, or retrieving further payloads.

Impact Assessment

Successful exploitation provides arbitrary command execution under the invoking user's privileges. The accessible scope may include local project files, user- ...[truncated 367 chars]

Remediation
View remediation

Remediation Suggestions

  • Remove the direct curl | bash execution pattern.
  • Pin installation instructions to a specific, immutable CLI release and version.
  • Download the installer or release artifact to a local file without executing it.
  • Verify a publisher-provided cryptographic signature or a securely distributed, pinned SHA-256 checksum.
  • Prefer an authenticated operating-system package manager or an official signed release package.
  • Allow inspection of the downloaded artifact before installation.
  • Execute installation with ordinary user privileges unless elevated access is demonstrably necessary.
  • Document the files, network access, and permissions required by the installer.

T03 · Remote Payload Retrieval and Execution

Error
Location
SKILL.md:72
Finding

Unverified Remote PowerShell Script Execution on Windows

Content
View full analysis

Vulnerability Details

File Location: SKILL.md:72
Vulnerability Type: Remote payload retrieval and immediate PowerShell execution
Risk Level: High

Complete Code Snippet:

powershell
irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell

Technical Analysis

The instruction uses Invoke-RestMethod through its irm alias to retrieve a mutable remote PowerShell script and pipes the result to Invoke-Expression through its iex alias. Invoke-Expression treats the downloaded response as executable PowerShell code immediately.

No fixed release, signature, Authenticode validation, checksum, or local review step is required. Consequently, the code that executes can differ from the content available when the Skill was audited. HTTPS alone does not protect against compromise of the remote server, domain, publishing credentials, or release infrastructure.

Installation guidance is relevant when the required CLI is absent, but executing mutable network content directly is not necessary for the Skill's declared Streamtime operations and violates least-trust installation practices.

Attack Path

  1. The oo CLI is unavailable on a Windows system.
  2. The agent or user follows the documented PowerShell setup command.
  3. irm downloads the current response from https://cli.oomol.com/install.ps1.
  4. The response is passed directly to iex.
  5. PowerShell interprets and executes the response without integrity validation.
  6. If the endpoint or distribution pipeline has been compromised, attacker-controlled commands run with the invoking user's permissions.

Impact Assessment

Exploitation enables arbitrary PowerShell execution as the invoking account. An attacker could read user-accessible files and environment variables, access available credentials or authenticated sessions, alter profile and configuration files, install additional payloads, or modify other writable resou ...[truncated 210 chars]

Remediation
View remediation

Remediation Suggestions

  • Remove the irm | iex execution pattern.
  • Pin the CLI to a specific immutable release.
  • Download the PowerShell installer or signed release package to disk before execution.
  • Validate Authenticode signatures and the expected publisher identity, or verify a securely distributed pinned checksum.
  • Prefer an official signed MSI, Microsoft Store package, or trusted package-manager source where available.
  • Present the installation command separately from the download and verification steps.
  • Run the installer without administrative privileges unless elevation is strictly required and clearly justified.
  • Document the installer's expected system changes and required permissions.
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
98% confidence
Finding

The skill instructs users to install software via a remote script piped directly into a shell (curl ... | bash). If the install endpoint, transport, or hosting environment is compromised, arbitrary code will execute immediately on the user's machine without an opportunity to inspect the script first. In a skill context, this is especially dangerous because the agent may surface or follow operational setup guidance during task execution, normalizing unsafe installation behavior.

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 manifest description says to use this skill for "ANY Streamtime request," covering reading, creating, and updating data without narrower constraints or exclusion examples. This is broad enough to match many ordinary requests involving Streamtime and does not clarify scope boundaries for when the skill should not be invoked.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.