Back to skill

Security audit

profileAPI

Security checks for vulnerabilities and agentic risk

Overview

The lookup workflow fits its purpose, but its setup path can introduce persistent changes to other agent skills without clearly disclosing that scope.

Review the CLI setup separately before allowing automatic installation. Its documented startup behavior can install or synchronize skills across agent applications; the documented OO_SKILLS_SYNC_DISABLED setting provides an opt-out. The remote installer contents and exact release remain unverified. Only submit email addresses or phone numbers you intend to share with OOMOL and profileAPI.

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 (5)

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
98% confidence
Finding

The supplied command executes an installer from cli.oomol.com and contains no profileAPI interaction. Nothing in the supplied description or code establishes this installer as a necessary supporting component for profileAPI access. Remote installer execution is materially different from the declared data-search and reading purpose. The downloaded script's contents and further effects are not visible in this chunk.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
88% confidence
Finding

The supplied chunk performs only a login operation, rather than the declared profileAPI data access. Authentication could be a supporting implementation detail if tied to profileAPI, but the supplied code establishes no such connection.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
98% confidence
Finding

The setup command executes a mutable remote script directly in Bash without a pinned version or independently verified integrity; the PowerShell alternative has the same issue. Compromise of the distribution infrastructure could therefore execute arbitrary code with the agent process's permissions, exposing local files and credentials. Restricting installation to a missing-CLI error reduces exposure but does not remove the supply-chain risk.

Content

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

The action workflow omits a privacy warning that reverse lookups transmit email addresses or phone numbers to third-party services.

Medium
Category
Output Handling
Confidence
94% confidence
Finding

The skill instructs the agent to execute connector actions with their input payloads, including email addresses and phone numbers for reverse lookups. Although it identifies the services involved, it does not warn that these personal identifiers are transmitted through OOMOL to profileAPI; labeling untagged reads as safe to run directly overlooks this privacy impact.

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