Back to skill

Security audit

Cronlytic

Security checks for vulnerabilities and agentic risk

Overview

Cronlytic operations have clear approval controls, but dependency setup can execute unverified downloaded code and introduce additional agent skills without clearly explaining those changes.

Review dependency setup before enabling this skill. Use a reviewed CLI release and approve its local changes separately; the remote installer contents remain unverified. If additional agent skills are unwanted, upstream documents OO_SKILLS_SYNC_DISABLED=1 to disable startup synchronization. Keep confirmation enabled for Cronlytic changes and deletions, and ensure you trust OOMOL to broker account access. [CLI controls](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md)

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

The supplied command installs software from an Oomol endpoint rather than performing Cronlytic operations. Nothing in the supplied chunk establishes this installation as a supporting dependency for Cronlytic. The downloaded script's contents and subsequent effects are not available for assessment.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
98% confidence
Finding

Piping an HTTPS response directly into Bash executes mutable remote content with the local process's permissions, without version pinning or independent integrity verification. A compromised distribution endpoint could therefore deliver code that accesses local secrets or alters files; the legitimate installation context and missing-CLI condition limit exposure but do not eliminate that supply-chain risk.

Content

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

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

Medium
Category
Output Handling
Confidence
95% confidence
Finding

The missing-CLI fallback directs the agent to execute downloaded installation scripts without first obtaining explicit approval for local code execution and system changes. Restricting this to a missing dependency reduces exposure, but the skill's confirmation rules only cover Cronlytic actions and do not explicitly protect this installation step.

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