Veriphone

Security checks across malware telemetry and agentic risk

Overview

This skill is a straightforward Veriphone connector that checks credits and verifies phone numbers through OOMOL, with no evidence of hidden data access or malicious behavior.

Install this only if you are comfortable using OOMOL as an intermediary for Veriphone requests. Phone numbers you verify will be sent through the OOMOL connector to Veriphone, and first-time setup may require installing the oo CLI from OOMOL’s remote installer.

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 description says to use this skill for "ANY Veriphone request" and "Whenever a task involves Veriphone," which is very broad and lacks constraints or negative examples. In a manifest/markdown context, this can overlap with many ordinary mentions of Veriphone and does not clearly define when the skill should or should not activate.

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