Back to skill

Security audit

Komos

Security checks for vulnerabilities and agentic risk

Overview

The Komos workflow has sensible safeguards, but its automatic setup can execute an unverified remote installer without separate user approval.

Review and approve CLI installation separately before allowing setup commands. Check its agent-skill installation behavior and connect only the intended Komos account. Keep the existing confirmation requirements for queueing and cancellation. The remote installer and live connector implementation were not verified; the artifacts do not establish 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 code performs remote installer execution rather than any visible Komos data operation. Although installation can be a supporting implementation detail, this chunk establishes no relationship between the Oomol installer and the declared Komos functionality. The downloaded script's contents and further effects are not available for assessment.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
97% confidence
Finding

Piping an unpinned HTTPS response directly into Bash executes whatever the installation endpoint serves with the invoking user's privileges; the PowerShell alternative has the same trust problem. A compromised distribution endpoint or delivery pipeline could therefore execute arbitrary local code, although the supplied content provides no evidence of such compromise. The missing-CLI condition and declared Bash tool restriction reduce reachability but do not make the installation instructions safe.

Content

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

Fallback setup executes downloaded installation scripts without warning about local code execution and system changes.

Medium
Category
Output Handling
Confidence
94% confidence
Finding

The missing-command fallback directs the agent to execute a remote installer without explaining its local execution privileges or requiring approval for system changes. Restricting setup to a genuine missing-dependency error reduces exposure, but authorization to perform Komos operations does not necessarily authorize installing local software.

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