Back to skill

Security audit

Plain

Security checks for vulnerabilities and agentic risk

Overview

The Plain workflow is clearly scoped, but setup instructs the agent to run an unchecked remote installer without asking for approval.

Review and install the CLI separately using a verified, pinned release before allowing the skill to run. Decide whether to permit automatic synchronization of agent skills. Connect only the intended Plain account and review each customer change. The bundled instructions were fully inspected, but the downloaded installer and remote connector were not audited.

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 (5)

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
98% confidence
Finding

The supplied code installs or runs externally supplied software rather than showing any Plain data operations. Nothing in the provided chunk establishes that this installer is a supporting dependency for Plain. The remote script's contents are not supplied, so its additional behavior cannot be assessed.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
84% confidence
Finding

The supplied code only invokes a login command and contains no identifiable Plain integration or data operations. Authentication could be a supporting implementation detail if oo were established as a Plain client, but the supplied material provides no such connection.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
98% confidence
Finding

The command streams a mutable remote script directly into Bash without artifact verification or a review checkpoint. HTTPS protects transport but does not prevent malicious code being served through a compromised vendor site or release pipeline, potentially exposing local credentials and files; the PowerShell alternative has the same underlying risk.

Content

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

First-time setup instructs execution of downloaded installer scripts without warning about running remote code or modifying the local system.

Medium
Category
Output Handling
Confidence
94% confidence
Finding

The missing-CLI fallback instructs the agent to execute downloaded shell or PowerShell code without first obtaining installation approval or verifying the artifact. This expands a Plain data task into local software installation; a compromised installer source could execute arbitrary code with the invoking user's privileges, although the fallback condition limits exposure.

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