Back to skill

Security audit

Systeme.io

Security checks for vulnerabilities and agentic risk

Overview

Account changes require approval, but setup can execute an unverified remote installer without separate user consent.

Review the CLI dependency before use and require separate approval for installation. Prefer a verified, fixed release and review or disable automatic skill synchronization. Connecting Systeme.io entrusts OOMOL with account credentials and business data. Keep the required confirmations for account changes. The remote installers and hosted connector were not verified; no malicious behavior was established.

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 chunk only executes an Oomol CLI installation script; it contains no visible Systeme.io integration or data-management behavior. Although installing dependencies can be a supporting implementation detail, the supplied content establishes no connection between this installer and the declared purpose. The remote script's contents and further effects cannot be determined from this chunk.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
98% confidence
Finding

Piping a remote installer directly into bash executes whatever the endpoint returns with the invoking user's permissions, without a pinned version or independent integrity verification. The endpoint is consistent with the documented CLI provider and setup is conditional, but compromise of its distribution infrastructure could still permit local data theft or modification; the PowerShell alternative has the same underlying risk.

Content

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

The fallback setup instructs the agent to execute remote installer scripts without warning the user about the system-level effects.

Medium
Category
Output Handling
Confidence
92% confidence
Finding

The fallback directs installation of local software without requiring disclosure of its effects or explicit user approval. Although installation only follows a missing-command error, the confirmation requirements cover Systeme.io mutations rather than local installation, allowing an account-management task to unexpectedly modify the user's environment.

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