Back to skill

Security audit

Mixpanel

Security checks for vulnerabilities and agentic risk

Overview

The Mixpanel workflow is coherent, but its setup instructions can execute unverified remote code without a separate approval step.

Review the setup before installing. Use a verified, versioned CLI installation and require approval for installation changes. Review its bundled-skill synchronization behavior, connect only the intended Mixpanel account, and consider OOMOL's access to your analytics data. The remote installer payload remains unverified; the artifact does not establish malicious intent.

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 chunk performs remote script execution rather than any identifiable Mixpanel operation. Although installing a CLI could be a supporting implementation detail, this chunk establishes no relationship between the Oomol installer and the declared Mixpanel capabilities. The downloaded script is not provided, so its further behavior cannot be assessed.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
98% confidence
Finding

Piping a network response directly into bash executes whatever the endpoint returns without a review or integrity-check step. HTTPS protects transport but does not prevent a compromised publisher or distribution service from supplying malicious code; this is the same underlying installation risk identified by SQP-2, not an independent exploit.

Content

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

The setup workflow executes remote installation scripts without a system-integrity warning.

Medium
Category
Output Handling
Confidence
93% confidence
Finding

The fallback setup directs the agent to execute remotely supplied shell or PowerShell code without inspection, integrity verification, or explicit approval for installing software. A compromised distribution endpoint could therefore execute arbitrary commands with the agent process's privileges; restricting installation to a missing-CLI error reduces exposure but does not establish trust in the downloaded code.

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