Back to skill

Security audit

Enigma

Security checks for vulnerabilities and agentic risk

Overview

The skill is coherent for operating Enigma through OOMOL, but its setup instructions include unverified remote installer commands that can execute changing external code on the user's machine.

Review the setup path before installing. Use this skill only if you trust OOMOL and Enigma access through your connected account, and avoid running the provided remote installer commands unless you have independently verified the installer source and understand it will execute code on your machine. Confirm all write and delete actions carefully because the skill can create, submit, and delete Enigma data.

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

Unverified Remote Installation Scripts Executed Directly by Shells

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, lines 66–70
Vulnerability Type: Remote mutable code 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 installation instructions retrieve mutable scripts from an external server and immediately execute them using Bash or PowerShell. Neither installation path pins a script version, validates a cryptographic checksum or publisher signature, nor allows inspection before execution.

HTTPS protects the connection in transit but does not ensure that the returned script is safe. If the OOMOL website, DNS, CDN, TLS infrastructure, deployment pipeline, or publisher account is compromised, an attacker can replace the installation script with arbitrary code. The effective payload can also change after the Skill package has been reviewed.

Directly piping curl into bash and piping Invoke-RestMethod into Invoke-Expression create equivalent remote-code-execution channels. Installing the CLI this way is not necessary for the Skill's declared Enigma operations and exceeds the minimum privileges required to document or invoke the connector.

Attack Path

  1. The user or Agent attempts to use the Skill on a system where the oo CLI is unavailable.
  2. The documented fallback instructs the user or Agent to execute one of the remote installation commands.
  3. An attacker compromises or gains control over the remote script delivery infrastructure, including the origin server, deployment account, DNS, or CDN.
  4. The server supplies an attacker-controlled script instead of the expected installer.
  5. Bash or PowerShell executes the response immediately without integrity or authenticity verification.
  6. The payload runs with the privileges of the invoking user and may inspect files, steal credentials ...[truncated 1134 chars]
Remediation
View remediation

Remediation Suggestions

  1. Remove both download-to-shell installation commands from the Skill instructions.
  2. Treat CLI installation as a separate, user-controlled prerequisite rather than an automatic fallback performed during Skill execution.
  3. Prefer a reputable operating-system package manager or an official signed package, pinned to an explicit version.
  4. If direct artifact downloads are unavoidable:
    • Use an immutable, versioned release URL.
    • Download the artifact to disk without executing it.
    • Publish and verify a SHA-256 or stronger cryptographic digest through a separately protected channel.
    • Verify a trusted publisher signature before execution.
    • Display the source, version, and requested actions to the user.
    • Obtain explicit user approval before running the verified installer.
  5. Do not execute installers with administrative privileges unless installation genuinely requires them and the user has explicitly approved the elevation.
  6. Document the minimum required filesystem, network, and account permissions.
  7. For automated environments, use a preinstalled, integrity-verified CLI image or package with a locked version and controlled provenance.

A safer conceptual workflow is:

bash
# Download an immutable, versioned artifact without executing it.
curl -fSLo oo-installer.sh "https://trusted.example/releases/<pinned-version>/install.sh"

# Compare against a separately published expected digest.
sha256sum oo-installer.sh

# Inspect and execute only after verification and explicit user approval.
less oo-installer.sh
bash oo-installer.sh

The actual implementation should use the vendor's official signed and version-pinned distribution mechanism rather than the placeholder URL shown above.

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 recommends piping a remotely fetched installer script directly into a shell (curl ... | bash), which creates a supply-chain and remote code execution risk if the distribution endpoint, transport, or script contents are compromised. Because this appears in a setup flow inside an agent skill, an automated system or user may execute it with little scrutiny, increasing the chance of arbitrary code execution on the host.

Content

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

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The description says to use this skill for "ANY Enigma request," including reading, creating, updating, and deleting data. That activation guidance is extremely broad and overlaps with many ordinary Enigma-related tasks, without constraints or exclusion examples, increasing the chance of unintended invocation.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.