Back to skill

Security audit

Numverify

Security checks for vulnerabilities and agentic risk

Overview

The phone lookups fit the stated purpose, but automatic setup executes unverified remote code without clearly controlling its broader effects.

Review the CLI installation separately before allowing automatic setup, including whether it installs or updates other agent skills. Prefer a reviewed, pinned installation and restrict unwanted skill synchronization. Only submit phone numbers you intend OOMOL and Numverify to process. The bundled instructions were fully inspected; the downloaded installers and hosted implementation remain outside that inspection.

Vulnerability Patterns
  • 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
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Output HandlingUnvalidated Output Injection, Cross-Context Output, Unbounded Output
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Findings (4)

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

The supplied code performs no visible Numverify search or read operation. Instead, it fetches and executes an installer from a different service. Nothing supplied establishes that installer as a supporting dependency for Numverify, making this an undeclared capability and materially different behavior. The downloaded script's further actions cannot be determined from this chunk.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
98% confidence
Finding

The setup command executes a remotely retrieved, mutable script immediately without a pinned version or independent integrity verification; the PowerShell alternative has the same weakness. Compromise of the distribution endpoint or installer supply chain could execute arbitrary code with the agent's local permissions, exposing files and credentials or modifying the environment. The missing-CLI condition limits when this happens but does not mitigate the consequences once installation runs.

Content

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

Phone-number validation lacks a warning about transmitting personal data to external services.

Medium
Category
Output Handling
Confidence
93% confidence
Finding

The workflow instructs the agent to execute Numverify actions through OOMOL, including phone-number validation, but the safety section treats all untagged reads as safe to run directly. It does not warn that validation sends the submitted phone number through OOMOL to Numverify; a read-only lookup can still affect privacy.

Content

No source excerpt is available for this finding.

Autonomous Decision Making

Medium
Category
Excessive Agency
Confidence
80% confidence
Finding

Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Content

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

md
- **`OOMOL_INSUFFICIENT_CREDIT`** — OOMOL billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.

- **HTTP 402 without `OOMOL_INSUFFICIENT_CREDIT`** — the third-party account itself has no active plan or credit. Report the provider error message as is; do not ask the user to recharge OOMOL.

## Resources