Back to skill

Security audit

Metaso

Security checks for vulnerabilities and agentic risk

Overview

The Metaso integration is coherent, but its setup executes unverified remote installers and leaves broader changes to your agents unexplained.

Review setup before allowing the agent to install software. Prefer a pinned, independently verified CLI installation and approve its local changes explicitly. The publisher documents OO_SKILLS_SYNC_DISABLED=1 to prevent startup skill synchronization; configure it before invoking the CLI if those changes are unwanted ([command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md#environment-variables)). Metaso requests pass through OOMOL, so connect only the account and permissions you intend to use. Remote installer contents were not verified; no malicious payload 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
94% confidence
Finding

The supplied chunk performs remote installation rather than any visible Metaso operation. Installing a dependency could be a supporting implementation detail, but this chunk establishes no relationship between the Oomol installer and Metaso. The contents and further effects of the downloaded script are not available, so no additional behavior or malicious intent can be concluded.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
98% confidence
Finding

Piping a downloaded script directly into Bash executes mutable remote content with the agent process's local privileges, without prior inspection or independent integrity verification. A compromised installer endpoint or publishing pipeline could therefore cause arbitrary local code execution; the documented dependency and HTTPS URL do not eliminate that supply-chain risk. The PowerShell installation alternative has the same underlying weakness.

Content

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

The setup workflow executes downloaded installer scripts without warning about remote code execution or local system changes.

Medium
Category
Output Handling
Confidence
94% confidence
Finding

When the CLI is missing, the workflow instructs the agent to execute a remote installer without an explicit approval step or disclosure of local system changes. The conditional setup context reduces exposure, but a request to use Metaso does not necessarily authorize installing executable software on the user's machine.

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