Back to skill

Security audit

Cuttly

Security checks for vulnerabilities and agentic risk

Overview

The Cuttly workflow fits its purpose, but its setup fallback runs downloaded code without clear installation approval or limits on local changes.

Review and approve CLI setup separately before allowing this skill to install anything. Prefer a verified, pinned installation and check whether it will install or update other agent skills. Cuttly requests pass through OOMOL, and link creation requires confirmation. No malicious behavior was established, but the external installer's exact changes could not be verified.

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

The supplied code installs software from an external service rather than performing the declared Cuttly operations. Although dependency installation can be a supporting implementation detail, the supplied content does not establish this installer's role in supporting Cuttly. The remote script's contents and further effects cannot be determined from this code 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 HTTPS response directly into Bash, allowing the installer endpoint to supply arbitrary code with the invoking user's permissions; the PowerShell alternative has the same trust issue. A compromised distribution endpoint could therefore lead to local file access, credential theft, or persistence, although the legitimate vendor domain and missing-CLI-only trigger reduce exposure and do not establish malicious intent.

Content

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

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

Medium
Category
Output Handling
Confidence
94% confidence
Finding

The missing-CLI fallback instructs the agent to execute downloaded installation code without explaining its privileges or local changes and without requiring installation-specific approval. The conditional trigger limits exposure, but the workflow can still turn a Cuttly request into unreviewed local software installation; this overlaps with SC2 rather than representing an independent execution mechanism.

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