XYDC MCP

• Outcome: Review
• Latest audit: Nov 3, 2026 · 12:05 PM UTC
• Version: 1.0.3

Overview

The XYDC integration is coherent, but its setup can execute an unverified remote installer and introduce persistent agent skills without clearly explaining those changes.

Review setup before enabling this skill. Install a verified CLI release yourself and require approval for subsequent software installation. Consider disabling startup skill synchronization with OO_SKILLS_SYNC_DISABLED=1, as documented in the CLI reference. OOMOL mediates connected-account access, and analysis calls can spend credits. The remote installers remain unverified; no artifact evidence establishes malicious intent.

A.I.G

Vulnerability Patterns

• Skill Instruction Hijacking: Alters the agent's session goals or safety constraints when the skill loads
• Agent Memory Poisoning: Writes attacker-controlled rules into memory that affect later sessions
• Remote Payload Retrieval and Execution: Fetches external code whose behavior can change after review
• Embedded Malicious Code: Ships malicious scripts inside the skill and executes them locally
• Unauthorized Access and Privilege Escalation: Obtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns

• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code
• Excessive Agency: Unrestricted Tool Access, Autonomous Decision Making, Scope Creep
• MCP Tool Poisoning: Hidden Instructions, Unicode Deception, Parameter Description Injection
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration

Findings (3)

Description-Behavior Mismatch

High

• Category: MCP Tool Poisoning
• Confidence: 93% confidence

Finding

The supplied chunk performs remote software installation, not XYDC MCP data operations. Installation could be a supporting implementation detail if a dependency relationship were established, but none is shown here. The downloaded script's contents and further effects 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 instructions pipe a remotely downloaded, unpinned script directly into Bash without integrity verification or inspection; the PowerShell alternative uses the same download-and-execute pattern. Compromise of the installer delivery infrastructure could execute arbitrary commands with the invoking user's privileges. Restricting installation to a missing-CLI error reduces exposure but does not secure execution, and the text does not require explicit installation approval.

Content

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

• 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

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