Back to skill

Security audit

Smooth

Security checks for vulnerabilities and agentic risk

Overview

Smooth actions require approval, but setup can execute unchecked remote code and the required CLI can silently install additional agent skills.

Review the local setup before enabling this skill. Install a verified CLI release yourself and require approval for installation changes. The CLI documents OO_SKILLS_SYNC_DISABLED=1 to prevent startup skill synchronization ([command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md)). Keep explicit approval for browser tasks and profile changes, and consider which account sessions Smooth will retain. The remote installer and hosted connector implementation remain outside the inspected package.

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

The supplied command executes externally supplied code from cli.oomol.com rather than performing Smooth operations. Although dependency installation can be a supporting implementation detail, nothing supplied establishes this installer as a dependency for Smooth. The downloaded script's contents and resulting system changes are not visible in this chunk.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
96% confidence
Finding

The command pipes a mutable remote script directly into Bash without pinning its version or verifying its integrity; the PowerShell alternative has the same trust problem. HTTPS protects transport but does not prevent a compromised distribution endpoint from supplying code that can access local files and credentials with the invoking user's privileges.

Content

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

Fallback setup runs downloaded installation scripts without warning about executing remote code or modifying the local system.

Medium
Category
Output Handling
Confidence
92% confidence
Finding

The fallback directs installation of executable software without explicitly requiring user approval or explaining that downloaded code will run with the invoking user's privileges. Although limited to a missing prerequisite, this can turn an ordinary Smooth request into an unexpected local system modification and expose the host if the installer is compromised.

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