Back to skill

Security audit

TimelinesAI

Security checks for vulnerabilities and agentic risk

Overview

The TimelinesAI workflow has clear safeguards, but its automatic remote installer needs review before use.

Review and approve a specific CLI release separately before allowing automatic setup, including any additional agent skills it installs. OOMOL handles your connected service credentials and requests. Keep exact-payload confirmation for WhatsApp sends. The remote installers were unavailable for inspection; no malicious behavior was established.

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

The supplied code performs remote installer execution rather than any visible TimelinesAI operation. No evidence establishes this installer as a supporting dependency for the declared purpose. The downloaded script's contents are not supplied, so its subsequent actions 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 mutable external code without a version pin or independent integrity verification. HTTPS protects transport but does not prevent a compromised publisher or distribution endpoint from serving code that steals accessible credentials or modifies local files; this is the same underlying installation risk highlighted by SQP-2.

Content

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

The setup workflow executes downloaded installation scripts without warning the user about remote code execution or system changes.

Medium
Category
Output Handling
Confidence
94% confidence
Finding

The fallback setup instructs execution of downloaded shell or PowerShell code without explaining its privileges, system changes, or requiring explicit installation approval. Triggering setup only when the CLI is missing limits exposure, but a routine TimelinesAI request can still lead to arbitrary code execution with the invoking user's privileges if the remote installer is compromised.

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