ClawHub
Back to skill

Security audit

Guru

Security checks for vulnerabilities and agentic risk

Overview

The Guru reading workflow is coherent, but missing software can trigger an unverified remote installer without clear user approval.

Review the CLI installation and its additional skill installation behavior before allowing setup. Require approval for local changes and prefer a pinned, integrity-verified release. Connect only the intended Guru account with read access through OOMOL. The remote installer contents and server-side credential handling could not be verified; no malicious behavior was established.

A.I.G

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

SkillSpector

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

The supplied chunk contains no Guru search or read functionality. Instead, it executes an installer hosted on cli.oomol.com. No connection between this installation and the declared Guru functionality is established, so this is an undeclared capability and an inconsistent resource rather than a demonstrated supporting implementation detail. The remote script's contents and any further effects are not visible.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
99% confidence
Finding

The command pipes a mutable remote script directly into Bash without pinning a version or verifying its integrity; the PowerShell alternative has the same weakness. Compromise of the distribution endpoint could execute arbitrary code with the invoking user's privileges, potentially exposing local files and credentials. The domain is relevant to the documented CLI provider and execution is conditional, but neither fact eliminates the supply-chain risk.

Content

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

The setup workflow instructs execution of remote installation scripts without warning about local system changes.

Medium
Category
Output Handling
Confidence
94% confidence
Finding

A missing CLI triggers instructions to install software without first obtaining approval for local system changes. A user requesting a Guru search has not necessarily authorized software installation, and both installation examples execute remotely supplied code; the conditional setup requirement reduces exposure but does not establish consent.

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