Back to skill

Security audit

Klazify

Security checks for vulnerabilities and agentic risk

Overview

The Klazify integration is coherent, but its setup directs the agent to execute downloaded code without clear approval or integrity checks.

Review the setup before enabling this skill. Install a vetted CLI release yourself, explicitly approve local changes, and check its automatic skill-synchronization settings. OOMOL mediates requests and manages the connected Klazify credential. The downloaded installers' complete effects remain unverified.

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 installs or bootstraps software from an unrelated service rather than searching or reading Klazify data. No connection to the declared Klazify functionality is shown. The contents and further effects of the downloaded script are not available for assessment.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
91% confidence
Finding

The supplied chunk performs only authentication and contains no Klazify-specific operation. Authentication could support a Klazify integration, but the code provides no evidence of that relationship; its demonstrated purpose differs materially from the declared search-and-read functionality.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
98% confidence
Finding

The command pipes a mutable remote script directly into Bash without version pinning or integrity verification. If the distribution endpoint or its supply chain is compromised, attacker-controlled code would run with the agent process's privileges; HTTPS and the legitimate setup purpose do not eliminate that risk.

Content

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

The fallback setup instructs the agent to execute downloaded installation scripts without warning the user about remote code execution or local system changes.

Medium
Category
Output Handling
Confidence
94% confidence
Finding

The fallback directs the agent to execute downloaded shell or PowerShell code without first obtaining approval for software installation and local system changes. Although conditional on a missing dependency and relevant to the skill, this expands a data-reading task into code execution with the invoking user's privileges; tool restrictions may limit execution but do not make the instruction safe.

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