ClawHub
Back to skill

Security audit

Cronly

Security checks for vulnerabilities and agentic risk

Overview

Cronly changes require approval, but missing-dependency setup directs execution of changing remote code without separate installation approval.

Review the CLI installer and its automatic skill-installation behavior before allowing setup. Prefer a separately approved, verified CLI installation. Cronly writes and deletions have explicit approval safeguards, but the remote installers' exact changes could not be verified.

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

The supplied code performs remote installer execution rather than any visible Cronly operation. Nothing in the description or code establishes this installer as a supporting Cronly dependency. The downloaded script's contents are not supplied, so its subsequent behavior cannot be assessed.

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 without a pinned version, signature check, or prior inspection. Compromise of the installer endpoint or its delivery infrastructure could therefore enable arbitrary code execution, including theft of accessible credentials; its legitimate setup purpose and conditional invocation do not remove this supply-chain risk.

Content

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

First-time setup instructs execution of downloaded installation scripts without warning about remote-code execution or system changes.

Medium
Category
Output Handling
Confidence
94% confidence
Finding

The setup instructions direct execution of downloaded shell and PowerShell scripts without explaining their privileges or system changes, or requiring installation-specific approval. Although restricted to missing-CLI errors, this can turn a routine Cronly request into execution of unreviewed remote code with the invoking user's permissions.

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