ClawHub
Back to skill

Security audit

Weatherbit

Security checks for vulnerabilities and agentic risk

Overview

The skill is a coherent Weatherbit connector, but its first-time setup tells users to run unverified remote installer scripts directly in a shell.

Install only if you are comfortable using OOMOL's oo CLI and Weatherbit through an OOMOL-connected account. Before following the setup commands, prefer OOMOL's official install guide or a pinned, verifiable package, and avoid piping remote scripts directly into bash or PowerShell unless you have reviewed and trust the installer source.

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:57
Finding

Unverified Remote Installer Download and Immediate Execution

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, lines 57–61
Vulnerability Type: Remote payload retrieval and execution
Risk Level: High

Vulnerable Code:

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

The first-time setup instructions download mutable scripts from cli.oomol.com and immediately execute them through Bash or PowerShell. Neither command pins a version, verifies a cryptographic checksum or digital signature, nor gives the user an opportunity to inspect the downloaded content before execution.

HTTPS provides transport protection but does not establish that the installer remains safe over time. Compromise of the hosting infrastructure, publishing account, DNS path, or installer generation process could cause these documented commands to execute attacker-controlled code. The effective payload can also change after the Skill has been reviewed, so the behavior cannot be fully audited from the repository.

Installing the required CLI may be necessary for the declared Weatherbit integration, but immediate pipe-to-shell execution exceeds the minimum privilege and verification requirements needed to perform that installation.

Attack Path

  1. An attempted Weatherbit action fails because the oo CLI is unavailable.
  2. The Agent or user follows the first-time setup instructions.
  3. The system retrieves the current installer from https://cli.oomol.com/install.sh or https://cli.oomol.com/install.ps1.
  4. A compromised or malicious response is passed directly to Bash or PowerShell without integrity verification.
  5. The payload executes with the privileges of the user running the command.
  6. The payload can access resources available to that user and may install additional software or persistence mechanisms.

Impact Assessment

Succe ...[truncated 656 chars]

Remediation
View remediation

Remediation Suggestions

  1. Replace pipe-to-shell and Invoke-Expression installation commands with a version-pinned package or downloadable artifact.
  2. Download the installer to a local file without executing it immediately.
  3. Publish an expected SHA-256 or stronger checksum through a separately protected release channel and require verification before execution.
  4. Prefer signed release artifacts and verify the publisher's digital signature using a pinned, documented trust key.
  5. Present the downloaded script for inspection and require explicit user approval before execution.
  6. Run the installer with ordinary user privileges unless a specific, documented operation requires elevation.
  7. Document the files, directories, network endpoints, and configuration changes expected from installation.
  8. Prefer a trusted platform package manager with pinned versions and signature validation where available.
  9. For Bash, use a workflow such as download, checksum verification, inspection, and then explicit execution. For PowerShell, save the script to disk, validate its hash and Authenticode signature, and invoke the verified file without iex.

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 users to install the CLI by piping a remote script directly into a shell (curl ... | bash), which is a classic supply-chain and remote code execution risk. If the install endpoint, transport path, or hosting account is compromised, arbitrary code would execute immediately on the user's machine with the user's privileges.

Content

Scanner excerpt · SKILL.md (reported line 57)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 Weatherbit request" and "Whenever a task involves Weatherbit," which is a very broad activation condition. It does not provide limiting context, 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.