ClawHub
Back to skill

Security audit

BYD Remote Control

Security checks for vulnerabilities and agentic risk

Overview

This skill is clearly for BYD vehicle control, but it can trigger real vehicle actions using stored credentials without enough confirmation or safety scoping.

Install only if you are authorized to control the BYD account and vehicle. Configure BYD_VIN or BYD_VEHICLE_ALIAS before running commands, protect the .env file like a password, and avoid unattended automations for lock, horn/lights, or climate actions unless you add an explicit confirmation or approval step.

SkillSpector

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (4)

Missing User Warnings

Medium
Confidence
91% confidence
Finding
The skill enables real-world remote vehicle actions such as locking, flashing lights, and starting A/C, but provides no warning about physical-world effects, consent requirements, or the risk of unintended actuation. In this context, omission of safety guidance is more dangerous because the actions affect a real vehicle and could cause nuisance, confusion, privacy exposure, battery drain, or unauthorized control if invoked carelessly.

Missing User Warnings

Medium
Confidence
90% confidence
Finding
The setup instructions ask the user to store highly sensitive BYD account credentials and remote-control PINs for scripts that can operate a vehicle, but they provide no warning about credential handling, local file protections, or the safety implications of issuing remote commands. In the context of a vehicle-control skill, this increases the chance of insecure deployment or accidental misuse, which could lead to unauthorized access to vehicle functions or unintended physical/operational effects.

Missing User Warnings

Medium
Confidence
86% confidence
Finding
The script includes the vehicle VIN in the returned snapshot and prints that JSON directly to stdout. A VIN is a persistent unique identifier, and exposing it in logs, terminals, automation output, or monitoring systems can leak sensitive vehicle metadata and enable correlation of the user's vehicle across systems.

Missing User Warnings

Medium
Confidence
92% confidence
Finding
The script directly executes a remote vehicle action (`flash_lights`) after authentication checks, but provides no user-facing warning, confirmation, or dry-run safeguard before triggering the command. In the context of a reusable automation skill for BYD remote control, this increases the chance of accidental or scripted misuse that could startle people nearby, reveal vehicle location, or trigger nuisance actions without deliberate operator intent.

Static analysis

No suspicious patterns detected.