Elasticsearch

Security checks across malware telemetry and agentic risk

Overview

This is a coherent Elasticsearch read/search skill, with the main caution that users should intentionally install and trust the OOMOL CLI before using it with sensitive Elasticsearch data.

Install only if you trust OOMOL and are comfortable connecting it to Elasticsearch. Run the oo CLI installer yourself from a trusted source, and use least-privilege Elasticsearch credentials because queries can expose whatever indices and documents that account can read.

SkillSpector

By NVIDIA
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)

Vague Triggers

Medium
Confidence
95% confidence
Finding
The manifest says to use this skill for "ANY Elasticsearch request" and "Whenever a task involves Elasticsearch," which is a very broad trigger description. It does not narrow scope with explicit exclusions or negative examples, so ordinary tasks that merely mention Elasticsearch could match unintentionally.

External Script Fetching

High
Category
Supply Chain
Content
- **`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
Confidence
90% confidence
Finding
curl -fsSL https://cli.oomol.com/install.sh | bash

VirusTotal

64/64 vendors flagged this skill as clean.

View on VirusTotal