Tesla Fleet API

Security checks across malware telemetry and agentic risk

Overview

This is a coherent Tesla Fleet API helper, but it can access sensitive vehicle data and perform real remote vehicle actions when configured.

Install only if you want an agent to interact with your Tesla account and vehicle. Keep the workspace private, protect auth.json and private-key.pem, stop the signing proxy when finished, and require explicit confirmation before commands that affect the physical vehicle.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (3)

Lp3

Medium
Category
MCP Least Privilege
Confidence
93% confidence
Finding
The skill advertises and operationally depends on sensitive capabilities including environment access, file read/write, network access, and shell execution, yet it does not declare permissions explicitly. This weakens user and platform visibility into what the skill can do, making it easier to over-trust a skill that can handle OAuth secrets, tokens, cached vehicle data, and invoke remote vehicle-control workflows.

Missing User Warnings

Medium
Confidence
90% confidence
Finding
This skill enables privacy-sensitive reads (for example location, vehicle state, energy/device data) and state-changing remote commands such as unlocking, HVAC control, waking, and charge control, but the description lacks an explicit warning or consent-oriented notice. In this context, that omission is significant because users may invoke commands or expose sensitive telemetry without appreciating the real-world safety and privacy implications.

Missing User Warnings

Medium
Confidence
84% confidence
Finding
OAuth access and refresh tokens are persisted to auth.json on disk without any visible permission hardening, encryption, or explicit user warning. In a CLI that handles high-value Tesla Fleet API credentials, local token storage increases the risk of credential theft from other local users, backups, or malware, especially because refresh tokens can enable long-lived account access.

VirusTotal

66/66 vendors flagged this skill as clean.

View on VirusTotal