Back to skill

Security audit

Keepa

Security checks for vulnerabilities and agentic risk

Overview

The Keepa workflow is coherent, but its setup can execute unverified remote code and introduce broader, undisclosed changes to agent skills.

Review and verify the CLI installation separately before allowing setup. Disable automatic skill synchronization using the vendor-documented OO_SKILLS_SYNC_DISABLED setting if you only want Keepa access. Understand that OOMOL brokers the connection and requests may consume credit. The remote installers and hosted connector implementation were not verified.

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 chunk installs software through an external shell script; it does not demonstrate Keepa searching or data retrieval. Nothing supplied establishes this installer as a supporting dependency for Keepa, so its execution is an undeclared capability rather than a demonstrated implementation detail. The downloaded script's contents and further effects cannot be determined from this chunk.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
90% confidence
Finding

Authentication could be a supporting implementation detail if it were shown to enable Keepa access, but the supplied code establishes no such relationship. Its only visible action is a login operation, materially different from the declared Keepa search and reading purpose. The command alone does not establish which service is authenticated or how credentials are handled.

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 response directly into Bash without verifying a pinned artifact or trusted signature. HTTPS protects transport but does not protect against compromise of the distribution infrastructure, which could turn this legitimate dependency setup into arbitrary code execution on the host.

Content

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

The setup workflow executes remotely downloaded installation scripts without warning about the system-integrity implications.

Medium
Category
Output Handling
Confidence
96% confidence
Finding

The fallback setup instructs the agent to execute downloaded shell or PowerShell scripts without integrity verification or explicit approval for changing the host system. A compromised installer source could execute arbitrary code with the invoking user's privileges; the missing-CLI condition reduces exposure but does not make execution 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 90)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