Back to skill

Security audit

Formsite

Security checks for vulnerabilities and agentic risk

Overview

Review is needed because setup directs the agent to run downloaded installation code without asking, despite clear approval controls for Formsite changes.

Install a reviewed, fixed CLI release yourself before use and require approval for any subsequent installation or agent-skill changes. Understand that OOMOL mediates access to your connected Formsite account and submitted data. Keep the skill's explicit approvals for webhook changes. The concern is insufficient control over setup; the inspected artifact does not establish malicious intent, and the remote installers 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
96% confidence
Finding

The declared purpose is Formsite data management, whereas the supplied command executes a remote installer from a different service. Nothing in the supplied chunk establishes that this installation supports Formsite operations. The downloaded script's contents are unavailable, so its further behavior cannot be determined.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
98% confidence
Finding

Piping a mutable HTTPS download directly into bash executes remote content without review, version pinning, or an independent integrity check; the PowerShell alternative has the same weakness. Compromise of the installer distribution path could therefore execute arbitrary code with the invoking process's permissions, although there is no evidence that the vendor endpoint is currently malicious.

Content

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

The setup workflow executes downloaded installation scripts without warning about local system changes or requiring approval.

Medium
Category
Output Handling
Confidence
94% confidence
Finding

The fallback instructs an agent to install software by executing downloaded shell or PowerShell code without first obtaining approval for local system changes. Although triggered only when the CLI is missing, this expands a Formsite data request into local code execution with the agent's permissions; the declared tool restriction may limit execution but does not make the instructions safe.

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