Back to skill

Security audit

TomTom

Security checks for vulnerabilities and agentic risk

Overview

The TomTom workflow fits its purpose, but setup can execute unverified remote code and introduce additional agent skills without clear user control.

Review setup before enabling this skill: install a verified CLI release yourself and explicitly control its bundled-skill synchronization. Addresses and coordinates will pass through OOMOL to TomTom. The complete bundled artifact was reviewed, but remote installer contents and backend behavior remain unverified; 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 (5)

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

The supplied code performs remote installation rather than the declared TomTom data-access function. No connection between this installer and TomTom functionality is established, so it cannot be treated as a demonstrated supporting implementation detail. The downloaded script is not supplied, so its further actions cannot be determined.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
90% confidence
Finding

The only supplied command initiates a login flow, and nothing in the chunk connects that authentication to TomTom. Authentication could be a supporting implementation detail if that connection were established, but the supplied code instead has an authentication-only purpose that does not substantiate the declared TomTom functionality.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
97% confidence
Finding

The fallback pipes a mutable remote installer directly into a shell without a pinned version, integrity verification, or explicit installation approval; the PowerShell alternative has the same weakness. A compromised distribution endpoint could execute arbitrary code with the agent's local privileges, although the missing-CLI prerequisite limits when this path is reached.

Content

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

Search actions transmit potentially sensitive addresses and coordinates without a privacy warning.

Medium
Category
Output Handling
Confidence
90% confidence
Finding

The workflow instructs the agent to run connector actions, including address searches and coordinate lookups, and labels read actions safe to run directly. Although the file identifies OOMOL and TomTom, it does not warn that user-provided addresses, coordinates, or search terms are sent through OOMOL to TomTom; read-only operations can still disclose sensitive location information.

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