Back to skill

Security audit

Photoroom

Security checks for vulnerabilities and agentic risk

Overview

The Photoroom workflow is coherent, but its setup instructions can execute unverified remote code without clear user approval.

Review setup before installing. Install a verified CLI release yourself rather than allowing automatic execution of the fallback installers, and review its bundled-skill installation behavior. Approve the image-editing payload and understand that images pass through OOMOL and temporary connector storage. The complete bundled file was inspected; external installer and connector behavior remain unverified.

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

The supplied command installs software by executing remotely fetched code; it does not demonstrate any Photoroom operation. Although dependency installation can be a supporting implementation detail, the supplied content establishes no connection between this installer and the declared Photoroom functionality. The downloaded script's further behavior cannot be determined from this code 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 independent integrity verification or review; the Windows alternative has the same execution pattern. Compromise of the distribution endpoint could execute arbitrary code with the invoking user's permissions, exposing local files and credentials. The conditional setup trigger and declared oo-only tool scope reduce immediate exposure, but do not make the recommended installation method safe.

Content

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

Fallback setup executes remote installation scripts without warning about local system changes.

Medium
Category
Output Handling
Confidence
93% confidence
Finding

A missing-command error triggers instructions to install software without explicit user approval or an explanation of local changes. Although this is a legitimate dependency and only a fallback, the Photoroom write-confirmation rules do not clearly cover local installation, allowing an agent that follows the setup instructions to exceed the user's intended authorization.

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