Find your next open-source project

Search by name, purpose, or keyword — or paste a GitHub repository URL

zeratulhx/Tesla-drug

Security & Privacy

Man-in-the-middle toolkit that spoofs Tesla FSD config responses to a vehicle over a local hotspot.

201
150
Python
1 day old

What it does

The project sets up a Windows machine as a man-in-the-middle between a Tesla vehicle and its configuration backend. When the car pulls its feature configuration, the computer answers in place of the server with a payload that turns all FSD switches on. The default chain is: phone USB tethering supplies internet to the PC, the PC runs a hotspot, and the car joins that hotspot README.

Components include an HTTPS interception listener on 443, DNS redirection (dns_sink.py), an ARP-based traffic redirection path for router mode, a local dashboard on port 8900, and a payload.json that defines the response. A watchdog and hotspot keep-alive script handle long-running operation. The repository description labels the build as an unverified v14.3.8 unlock for the CN region repo.

Quick start

  1. Run 一键安装.cmd from the project. Accept the UAC prompt for firewall rules. Everything installs to C:\fsd-mitm, and desktop shortcuts appear.

  2. Connect the phone by USB, enable USB tethering, and confirm the PC has internet. Then run in PowerShell:

    C:\fsd-mitm\route-b.ps1 -Ssid FSD-PC -Key fsd2026!!
    
  3. Join the car to the FSD-PC Wi-Fi network; the car should receive a 192.168.137.x address with gateway and DNS at 192.168.137.1.

  4. Double-click the FSD一键启动 shortcut. It starts the 443 interception, DNS redirection and dashboard, and prints a status table.

  5. Reboot the car by holding both scroll wheels for about 10 seconds, then wait 5–10 minutes for the first configuration request. Open the dashboard at the local address dashboard and look for a HIT entry whose client is the car IP, with a byte count matching payload.json.

Status can be checked without restarting processes:

powershell -File C:\fsd-mitm\start_hotspot.ps1 -Status

The car is documented to request configuration every 12 hours ± 2 hours. Missing a hit shortly after reboot is not necessarily a failure.

Changing the payload

The response can be edited through the form endpoint config page, the JSON endpoint payload endpoint, or by editing C:\fsd-mitm\payload.json directly. Changes take effect on the next request without a restart. Rollback files payload-282b.json (original) and payload-16f.json (16-field version) are included. Setting mode.json to {"mode":"observe"} records traffic without replying.

Constraints

  • Windows only, installed to a fixed path C:\fsd-mitm; roughly 24 hard-coded paths mean changing the drive requires editing the scripts.
  • The installer creates a virtual environment and installs dependencies; -UseMirror switches pip to the Tsinghua mirror, and -Check performs a dry check without touching files.
  • Port 53 can be occupied by the Windows hotspot DNS proxy; the guide instructs stopping the occupying process before starting.
  • In router mode (start_all.cmd), target, gateway, local IP, interface and upstream IP are hard-coded in start_all.ps1 and must be adjusted for a different network. Router mode and hotspot mode are mutually exclusive.
  • Non-mock endpoints (music, notifications, weather) may return 400 because clients require certificates that cannot be reached upstream; the README states FSD delivery itself is unaffected.
  • No license is declared, and the repository calls the build unverified. The README does not explain whether the payload is valid for a given firmware or region beyond the v14.3.8 CN description.

The described interception and DNS/ARP redirection modify how a vehicle talks to its backend. Users should check applicable law and vehicle warranty terms; these are not safety guarantees.

HotRepo's take

In the 2026-11-20 new-project snapshot, the repository recorded 100 stars and 96 forks gained within a window starting on 2026-11-19, roughly eleven hours of observation. The near one-to-one star-to-fork ratio suggests many users copied or archived the project rather than only bookmarking it. No GitHub daily rank has been recorded, and there is only one snapshot, so that single point supports no trend claim. The implementation is a scripted Windows MITM stack with concrete status checks and rollback payloads, but the unverified label and the absence of firmware-specific documentation are the main limits on judging whether it works on a particular car.

Written by AI from the project's README, updated . The project's own docs are the source of truth.

You might also like

  1. hypery11/flipper-tesla-fsdA CAN-bus toolkit that modifies Tesla autopilot, FSD and telemetry frames from a Flipper Zero or ESP32.C++1,184