Back to skill

Security audit

Terminus App

Security checks for vulnerabilities and agentic risk

Overview

The Terminus features are appropriately controlled, but setup can execute changing remote code and introduce broader agent changes without clearly explaining them.

Review setup before enabling this skill. Install a verified CLI release yourself, review its managed-skill synchronization settings, and authorize the OOMOL connection with only the Terminus access needed. The remote installers were unavailable for inspection. Terminus writes require confirmation, and no artifact evidence establishes malicious intent.

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 runs an Oomol-hosted installer, with no visible connection to Terminus App or its data operations. Nothing in the supplied code establishes this installer as a supporting dependency for the declared purpose. The downloaded script's contents and further 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 a pinned version or independent integrity verification; the PowerShell alternative has the same execution pattern. If the distribution endpoint or release pipeline is compromised, attacker-controlled code could execute with the invoking user's privileges, exposing local files and credentials; HTTPS and the legitimate dependency relationship do not eliminate this supply-chain risk.

Content

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

Fallback setup executes remote installation scripts without warning about system-level effects.

Medium
Category
Output Handling
Confidence
94% confidence
Finding

The fallback directs the agent to install local software without first explaining the system changes or obtaining installation-specific approval. Its missing-command condition limits exposure, and enforced Bash(oo *) restrictions could block the installer, but neither makes the installation instructions themselves appropriately authorized.

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