Back to skill

Security audit

App Store Connect

Security checks for vulnerabilities and agentic risk

Overview

App Store changes require approval, but setup runs unverified remote installers and leaves broader agent-skill changes unexplained.

Review and install a verified, pinned CLI release separately before use, and connect only the App Store permissions needed. Consider disabling its automatic skill synchronization; the publisher documents OO_SKILLS_SYNC_DISABLED=1 for this purpose. Keep approval requirements for account changes. Exact installer effects remain unverified. [CLI controls](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md#environment-variables)

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

The supplied chunk performs remote script execution rather than any identifiable App Store Connect operation. Although installing tooling can be a supporting implementation detail, nothing supplied establishes this installer as a dependency for the declared functionality. 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

The curl-to-bash pipeline executes whatever script the remote endpoint currently serves, without a pinned version or independent integrity verification. A compromised distribution endpoint or malicious installer update could execute code with the agent's local privileges, potentially accessing workspace data or local credentials; HTTPS and the legitimate CLI dependency do not eliminate that supply-chain risk.

Content

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

First-time setup instructs the agent to execute downloaded installer scripts without warning the user about remote code execution or system changes.

Medium
Category
Output Handling
Confidence
94% confidence
Finding

The setup directs the agent to execute remote installers without explicitly obtaining approval for local code execution and system changes. Although this is a legitimate dependency and only runs when missing, a request to manage App Store Connect data does not itself authorize installing software with the agent's local privileges.

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