Back to skill

Security audit

ChaserHQ

Security checks for vulnerabilities and agentic risk

Overview

The skill is mostly a coherent read-only ChaserHQ connector, but its setup instructions include unverified remote installer commands that can execute arbitrary code.

Before installing, review the OOMOL CLI installation path carefully. Prefer an official package manager, a pinned release, or a downloaded installer with signature or checksum verification instead of running the pipe-to-shell commands directly.

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

Unverified Remote Installer Download and Execution

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, lines 62–66
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 pipe remotely retrieved content directly into a command interpreter. The effective code is not included in the reviewed Skill package and can change after the Skill has been audited. Neither command pins an installer version nor verifies a cryptographic signature or checksum before execution.

Although the download host is consistent with the named OOMOL service and installation is presented as a fallback when the oo command is unavailable, executing an installer is not required for routine ChaserHQ read operations when the CLI is already installed. Installation also has substantially broader effects than invoking the narrowly allowed oo connector commands. Consequently, these instructions exceed the minimum runtime privileges needed for the Skill's declared read-only functionality.

If the hosting infrastructure, installer publication process, DNS resolution, TLS trust chain, or vendor account is compromised, the downloaded response can contain arbitrary shell or PowerShell commands. The commands would execute with the privileges of the user or agent following the instructions.

Attack Path

  1. The oo CLI is unavailable, causing the first-time setup fallback to apply.
  2. The user or agent runs the documented installation command.
  3. curl or Invoke-RestMethod retrieves a mutable script from the external OOMOL endpoint.
  4. The response is passed directly to Bash or PowerShell without local inspection, version pinning, checksum validation, or signature verification.
  5. If the remote response has been maliciou ...[truncated 1095 chars]
Remediation
View remediation

Remediation Suggestions

  • Remove both pipe-to-interpreter installation commands from the Skill instructions.
  • Direct users to an authenticated official package repository or a specific, immutable release artifact.
  • Pin the CLI to a reviewed version rather than downloading a mutable installation endpoint.
  • Download the installer or package to disk without executing it automatically.
  • Publish and verify a cryptographic signature using a trusted, independently distributed public key. At minimum, verify a version-specific SHA-256 checksum obtained through a separate authenticated channel.
  • Abort installation if signature, checksum, expected origin, or version verification fails.
  • Allow the user to inspect the downloaded artifact and require explicit approval before execution.
  • Avoid requesting administrator or root privileges unless a documented installation step strictly requires them. Prefer installation into a user-owned directory.
  • Apply equivalent verification and approval controls to both the Bash and PowerShell installation paths.
  • Keep installation outside normal Skill execution. If oo is unavailable, return a clear error and provide a safe installation guide rather than automatically executing setup commands.
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 software via a network-fetched script piped directly into a shell, which executes unverified remote content immediately. If the install endpoint, transport, hosting, or supply chain is compromised, this can lead to arbitrary code execution on the user's machine.

Content

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

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The description says to use this skill for "ANY ChaserHQ request," which is a very broad activation condition without examples of scope boundaries or exclusions. In a manifest file, this can overlap with many ordinary tasks involving ChaserHQ and does not clearly define when the skill should or should not activate.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.