Garmin Connect CLI

Security checks across malware telemetry and agentic risk

Overview

This skill is a coherent Garmin Connect CLI helper, but it can access sensitive health data and account tokens that users should handle carefully.

Install this only if you want an agent to help operate your Garmin Connect account. Treat `gccli auth token` and `gccli auth export` output like passwords: do not paste tokens into chats, logs, repos, or unsecured files, and avoid copying them to untrusted machines. Require explicit confirmation before commands that create, upload, rename, retype, link, unlink, schedule, send, or delete Garmin data.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (1)

Missing User Warnings

Medium
Confidence
89% confidence
Finding
The skill explicitly documents `gccli auth export` and `gccli auth import <token>` and even suggests piping credentials to a file or copying them to another machine, but it does not warn that the exported token is effectively a bearer credential. That omission can lead users or downstream agents to store secrets insecurely, leak them via shell history/files, or transfer them to less-trusted systems, enabling account takeover of Garmin data.

VirusTotal

64/64 vendors flagged this skill as clean.

View on VirusTotal