Back to skill

Security audit

Xodo Sign

Security checks for vulnerabilities and agentic risk

Overview

The Xodo Sign workflow requires approval for account changes, but its setup allows remote code execution without sufficient controls or disclosure of broader agent changes.

Review and approve CLI installation separately before allowing automatic setup. Check its managed-skill behavior; current [vendor documentation](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md) provides OO_SKILLS_SYNC_DISABLED to prevent startup skill synchronization. Connect only the intended Xodo Sign account and retain confirmation for every write or destructive action. The remote installer and connector implementation were not verified; 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
98% confidence
Finding

The supplied code runs an Oomol-hosted installation script rather than performing an observable Xodo Sign operation. Although dependency installation can be a supporting implementation detail, the supplied chunk establishes no relationship between this installer and the declared service. The downloaded script's contents and any additional 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 command pipes a mutable remote script directly into Bash without verifying a pinned version, signature, or trusted checksum; the PowerShell example uses the equivalent fetch-and-execute pattern. Compromise of the installer hosting or release pipeline could execute attacker-controlled code with the invoking user's privileges, potentially exposing local files and credentials. The legitimate dependency relationship and HTTPS reduce suspicion of malicious intent but do not establish script integrity.

Content

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

The setup workflow executes remote installation scripts without a user-facing warning about code execution and system changes.

Medium
Category
Output Handling
Confidence
90% confidence
Finding

When the CLI is missing, the skill directs installation without explicitly obtaining approval for executing remote code or making local system changes. The conditional setup trigger limits exposure, but authorization to perform a Xodo Sign task does not necessarily authorize installing software on the host.

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