Back to skill

Security audit

Shortcut

Security checks for vulnerabilities and agentic risk

Overview

Shortcut changes require confirmation, but setup can run downloaded installation code on your computer without separate approval or integrity verification.

Review the installation fallback before use. Install a reviewed, version-pinned CLI separately and require approval for local installation or agent-skill changes. Consider whether OOMOL should handle your Shortcut credentials and workspace data, and retain confirmation for Shortcut writes. The bundled instructions support a setup-control concern, but provide no evidence of intentional malicious behavior; the external installer could not be inspected.

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 executes an Oomol-hosted installer rather than performing Shortcut operations. Nothing in the provided chunk establishes that this installer is a supporting dependency for Shortcut functionality. The downloaded script's contents are not supplied, so its further behavior cannot be determined.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
98% confidence
Finding

Piping a mutable HTTPS response directly into bash executes remote code with the agent process's local privileges, without a pinned version or independent integrity verification. A compromised installer endpoint or release pipeline could therefore expose accessible local secrets or modify the host; the PowerShell example has the same underlying risk. The documented dependency and missing-CLI condition explain the purpose and limit exposure, but do not remove this supply-chain risk.

Content

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

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

Medium
Category
Output Handling
Confidence
92% confidence
Finding

The setup instructions direct the agent to execute downloaded shell or PowerShell code when the CLI is missing, without requiring informed user approval for local installation. The confirmation rules cover Shortcut mutations, not local system changes, so an ordinary Shortcut request could unexpectedly lead to software installation.

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