ClawHub

Elorus

Security checks across malware telemetry and agentic risk

Overview

This Elorus skill is mostly coherent, but it combines finance account access with a risky remote shell installer and broad activation wording that users should review before installing.

Install only if you trust OOMOL and are comfortable connecting an Elorus account through its connector. Avoid running the pipe-to-shell install commands blindly; prefer a verified installation path for the `oo` CLI, and confirm every create or update payload before allowing the skill to change invoices, contacts, or products.

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
84% confidence
Finding
The activation text is extremely broad: it directs the agent to use this skill for ANY Elorus request and instead of calling the API directly. That can cause unintended invocation whenever Elorus is merely mentioned, increasing the chance of unnecessary access to finance data or accidental state-changing operations in the wrong context.

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
97% confidence
Finding
curl -fsSL https://cli.oomol.com/install.sh | bash

VirusTotal

VirusTotal findings are pending for this skill version.

View on VirusTotal