Back to skill

Security audit

Wiza

Security checks for vulnerabilities and agentic risk

Overview

The Wiza operations are clearly scoped, but setup directs the agent to execute an unverified remote installer without separate approval.

Review the setup behavior before installing. Install a verified CLI release yourself and require approval before any remote installer runs. Check whether the CLI will install or synchronize additional agent skills. Wiza changes already require confirmation, and OOMOL's role is disclosed. The remote installer and connector implementation remain unverified; no malicious behavior was established.

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
96% confidence
Finding

The supplied code installs software from an Oomol endpoint rather than performing Wiza operations. Nothing in the supplied chunk establishes this installer as a supporting dependency for Wiza, and the declared description does not disclose this installation behavior. The downloaded script's contents and further effects are not visible.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
98% confidence
Finding

The curl-to-bash pipeline immediately executes mutable remote content without verifying a pinned version, signature, or trusted checksum. HTTPS protects transport but does not prevent a compromised publisher or hosting endpoint from supplying code that can access local files and credentials.

Content

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

Fallback setup executes remote installation scripts without a system-integrity warning.

Medium
Category
Output Handling
Confidence
95% confidence
Finding

The fallback directs the agent to execute downloaded shell or PowerShell code without an integrity check or explicit approval for installing software. A compromised installer endpoint could execute arbitrary code with the agent's local privileges; limiting this to a missing-CLI error reduces frequency but not potential impact.

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 80)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