Back to skill

Security audit

Tick

Security checks for vulnerabilities and agentic risk

Overview

This Tick integration needs review because its setup can execute downloaded software without a separate approval or verification step.

Use a verified CLI release and require approval before installation. Review or disable its automatic agent-skill synchronization, connect only the intended Tick account, and retain the write/delete confirmations. OOMOL mediates Tick access. The remote installers and hosted connector were not verified; no malicious behavior was established in the supplied artifact.

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

The visible code installs software from a separate service rather than interacting with Tick. Although installation can be a supporting implementation detail, the supplied content does not establish that this installer supports Tick functionality. The fetched script is not provided, so its additional behavior cannot be determined.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
98% confidence
Finding

Piping a remotely fetched installer directly into Bash executes its contents with the invoking user's permissions without verifying a pinned artifact or signature. Compromise of the distribution endpoint could therefore lead to local code execution and access to user-readable credentials or files; HTTPS and the legitimate CLI dependency reduce some risks but do not establish artifact integrity.

Content

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

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

Medium
Category
Output Handling
Confidence
94% confidence
Finding

The setup instructions direct installation after a missing-command error without explicitly requiring approval for executing remote code or changing the local environment. A request to manage Tick records does not necessarily authorize software installation, although the conditional setup trigger limits exposure.

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