other
- Location
scripts/tesla-command.js:18- Finding
Sensitive vehicle credentials and control traffic routed through an undisclosed third-party proxy
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This Tesla remote-control skill is mostly coherent, but it routes vehicle credentials and commands through a third-party service with under-disclosed high-impact access.
Only install this if you intentionally trust tesla.dhuar.com with Tesla vehicle access, VINs, telemetry, and command traffic. Treat the stored apiKey as a sensitive vehicle-control secret, restrict file permissions manually, avoid using command-line history for the key, and prefer a version that uses official Tesla authorization directly or clearly documents the proxy operator and safety controls.
scripts/tesla-command.js:18Sensitive vehicle credentials and control traffic routed through an undisclosed third-party proxy
scripts/tesla-command.js:153API credential transmitted in URL query strings
scripts/init-tesla-config.js:64Plaintext API key stored without explicitly restrictive file permissions
The documentation claims the skill is based on Tesla's official Fleet API, but it instructs users to obtain an apiKey from the third-party domain tesla.dhuar.com and notes local reading of ~/.tesla_cn.json, with the key attached to requests. That mismatch is security-relevant because users may believe they are trusting Tesla directly while actually disclosing credentials and vehicle-control capability to an intermediary service, which could expose location, vehicle metadata, and remote command authority.
The skill exposes code capabilities that use local secrets and network access, but it does not declare any tool scope such as permissions or allowed-tools. This weakens user and platform visibility into what the skill can access, increasing the chance that a user will invoke a remote-control skill without understanding it can read ~/.tesla_cn.json and contact external services.
The script includes Chinese-only usage/documentation comments and Chinese user-facing output strings later in the file, indicating a fixed language choice. Under the policy, forcing a specific language without user opt-in is a natural-language policy violation unless the locale restriction is explicitly justified.
This appears to be a duplicate of the same session-persistence finding: the script writes a sensitive API key to ~/.tesla_cn.json in plaintext. In the context of a remote vehicle-control skill, credential exposure is more serious because the stored secret may enable access to Tesla account/vehicle operations if the local machine is compromised or shared.
});
} catch (e) {
console.error('error');
console.error('failed to write config file');
console.log(
JSON.stringify({
error: 'write_failed',
This appears to be a duplicate of the same session-persistence finding: the script writes a sensitive API key to ~/.tesla_cn.json in plaintext. In the context of a remote vehicle-control skill, credential exposure is more serious because the stored secret may enable access to Tesla account/vehicle operations if the local machine is compromised or shared.
});
} catch (e) {
console.error('error');
console.error('failed to write config file');
console.log(
JSON.stringify({
error: 'write_failed',
The code loads an API key from a local config file and appends it to the request URL as a query parameter sent to a third-party proxy domain. Putting secrets in URLs is dangerous because they may be exposed through logs, browser/history equivalents, proxy logs, monitoring systems, referrer leakage, or error reporting, and the use of a non-official intermediary materially increases the trust and exfiltration risk.
The script directly executes sensitive Tesla vehicle control commands such as locking doors, opening trunks, climate control, and boombox actions as soon as it is invoked. In a remote-control skill context, lack of an explicit confirmation or safety interlock increases the risk of accidental, spoofed, or unintended physical-world actions against a vehicle.
The script's inline instructions and at least one user-facing error message are presented in Chinese only, which imposes a specific language on users without opt-in or alternative locale support. This can violate language/locale policy when the skill does not document that it is intentionally region-specific.