ClawHub

Clockify

Security checks across malware telemetry and agentic risk

Overview

This appears to be a disclosed Clockify connector that uses OOMOL to access Clockify data, with notable setup and account-access cautions but no evidence of hidden or malicious behavior.

Install only if you intend to let an agent operate your connected Clockify account through OOMOL. Review Clockify OAuth/account scope, require explicit confirmation before creating, updating, or deleting time-tracking data, and avoid running the curl-to-bash installer unless you trust and have verified the OOMOL CLI source.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (2)

Vague Triggers

Medium
Confidence
83% confidence
Finding
The description instructs use of the skill for ANY Clockify request and instead of calling the API directly, which is broad enough to cause over-invocation whenever Clockify is mentioned. In an agent setting, this can lead to unintended tool execution paths, including state-changing operations, especially because the same skill exposes both read and write/delete actions.

External Script Fetching

High
Category
Supply Chain
Content
- **`oo: command not found`** — install the oo CLI (other platforms: <https://cli.oomol.com/install-guide.md>):

  ```bash
  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux
  ```

  ```powershell
Confidence
96% confidence
Finding
curl -fsSL https://cli.oomol.com/install.sh | bash

VirusTotal

64/64 vendors flagged this skill as clean.

View on VirusTotal