Back to skill

Security audit

Gist

Security checks for vulnerabilities and agentic risk

Overview

Gist changes require approval, but the setup fallback executes unverified downloaded code without a separate installation approval step.

Review the CLI installation separately before allowing this fallback. Prefer a reviewed, fixed release, confirm OOMOL's account permissions, and decide whether additional agent skills should be installed. Upstream documents OO_SKILLS_SYNC_DISABLED=1 to disable startup skill synchronization. Gist writes and deletions already have explicit approval safeguards; the remaining concerns are installation control and under-disclosed dependency behavior.

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 command performs no Gist operations. Instead, it fetches and executes an external installer, a materially different action with no established supporting role in the declared functionality. The downloaded script is 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
99% confidence
Finding

The command pipes a mutable remote script directly into Bash without verifying its integrity or authenticity beyond HTTPS; the PowerShell alternative has the same problem. A compromised installer host or publishing pipeline could execute arbitrary code with the agent's local privileges, exposing files and credentials even though Gist credentials are injected server-side. The legitimate dependency purpose and missing-CLI condition reduce exposure but do not remove this supply-chain risk.

Content

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

Automatic CLI setup lacks a warning about executing downloaded code and modifying the local system.

Medium
Category
Output Handling
Confidence
92% confidence
Finding

The fallback directs the agent to install software after a command-not-found error without first explaining that it will execute downloaded code and modify the local environment. Installation is a reasonable dependency-management step, but permission to perform Gist operations does not necessarily authorize local software installation; the conditional trigger limits exposure without providing consent.

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