Back to skill

Security audit

Zendesk

Security checks for vulnerabilities and agentic risk

Overview

Zendesk changes require your approval, but setup can execute unverified downloaded code and introduce additional agent skills without clearly scoped consent.

Review setup before enabling this skill. Prefer a separately approved, verified CLI installation, and disable managed-skill synchronization if you only want Zendesk functionality. The publisher documents OO_SKILLS_SYNC_DISABLED for that control. Understand that OOMOL mediates your connected Zendesk access, and retain the skill's confirmation requirement for changes. Remote installer contents and hosted connector behavior were not verified. [Publisher controls](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md)

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 chunk performs remote script execution rather than any demonstrated Zendesk operation. Dependency installation could be a supporting implementation detail, but nothing supplied establishes this installer's role in providing Zendesk functionality. The downloaded script's contents and further effects are unknown.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
98% confidence
Finding

Piping an HTTPS response directly into bash executes mutable remote content without a pinned version or independent integrity verification. HTTPS protects transport but does not prevent a compromised publishing account or server from supplying malicious code, which would run with the invoking user's privileges; the PowerShell alternative has the same issue.

Content

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

Fallback setup executes downloaded installation scripts without a system-integrity warning or explicit approval.

Medium
Category
Output Handling
Confidence
95% confidence
Finding

The fallback directs the agent to execute downloaded shell or PowerShell code without requiring explicit approval for local software installation. Although conditional on a missing dependency, this expands a Zendesk task into local code execution, potentially exposing user-accessible files and credentials if the installer or its distribution infrastructure is compromised.

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