Back to skill

Security audit

Everhour

Security checks for vulnerabilities and agentic risk

Overview

The Everhour integration has sensible account-change safeguards, but its automatic software setup needs review.

Review and install a verified CLI release separately before enabling this skill. Check whether it will install or update other agent skills; the CLI documents OO_SKILLS_SYNC_DISABLED for disabling that synchronization in its [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md). OOMOL will mediate access to your connected Everhour account. The remote installer payload and hosted service 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 (4)

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
98% confidence
Finding

The supplied code performs remote script execution rather than an Everhour operation. Although installing a dependency can be a supporting implementation detail, the provided content establishes no relationship between this Oomol installer and the declared Everhour functionality. The downloaded script's further behavior cannot be determined from this chunk.

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 mutable remote content without verifying its integrity or reviewing it first. A compromised installer source could access local files and credentials or modify the host under the invoking account; this is the same underlying installation risk identified by SQP-2, not evidence of a separate malicious payload.

Content

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

Fallback setup executes remotely downloaded installation scripts without a system-integrity warning.

Medium
Category
Output Handling
Confidence
96% confidence
Finding

The fallback directs execution of remotely downloaded shell and PowerShell scripts without an integrity check or explicit installation approval. If the distribution endpoint or delivery pipeline is compromised, the script could execute arbitrary commands with the invoking user's privileges; limiting setup to a missing-CLI error reduces exposure but does not eliminate this risk.

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