Back to skill

Security audit

KIE.AI

Security checks for vulnerabilities and agentic risk

Overview

The KIE.AI features fit the stated purpose, but setup can execute unverified downloaded code and make broader changes to your agent’s skills.

Review and approve CLI setup separately before enabling this skill. OOMOL mediates account access and stores the connected provider credentials. Consider disabling automatic skill synchronization using OO_SKILLS_SYNC_DISABLED=1, as documented in the publisher’s command reference. Remote installer contents and the downloaded release were not verified; no malicious payload 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 (5)

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

The supplied command performs remote installer execution rather than KIE.AI search or data retrieval. Nothing in the supplied code establishes that this installer is a supporting dependency for the declared purpose. The downloaded script's contents and resulting system changes cannot be determined from this chunk.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
86% confidence
Finding

Authentication can be a supporting implementation detail, but the supplied code contains only a login command and no demonstrated KIE.AI integration or data-access behavior. Its observable primary purpose therefore differs from the declared purpose.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
98% confidence
Finding

Piping the HTTPS response directly into bash executes whatever the installation endpoint supplies without pinning or verifying the code. A compromised distribution endpoint or altered installer could execute arbitrary commands with the agent's permissions, potentially exposing local credentials or modifying files; HTTPS alone does not protect against compromise of the publisher's distribution infrastructure.

Content

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

Fallback setup executes downloaded installation scripts without warning the user about remote code execution or local system changes.

Medium
Category
Output Handling
Confidence
96% confidence
Finding

When the CLI is missing, the skill directs the agent to execute a downloaded installer without a separate approval step or a stated integrity-verification procedure. This crosses from reading account data into executing code with the agent process's local permissions; the missing-command prerequisite reduces exposure but does not constrain what the installer can change or access.

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