ClawHub

Owl Protocol

Security checks across malware telemetry and agentic risk

Overview

This is a disclosed Owl Protocol connector skill with read actions and one confirmed write action, with setup risks that users should review before connecting an account.

Install only if you intend to use OOMOL with Owl Protocol. Review the oo CLI installer before running the pipe-to-shell command, connect only the Owl Protocol account/scopes you need, and require explicit confirmation before allowing token metadata updates.

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
94% confidence
Finding
The manifest says to use this skill for "ANY Owl Protocol request," covering reading, creating, and updating data, without narrowing the trigger scope or giving exclusion examples. This is broad enough that many loosely related mentions of Owl Protocol could match, increasing the risk of accidental invocation.

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