01Summary
The leak, reported on May 25, 2023, provided a comprehensive look into Tesla's internal service database logs spanning 2015 to 2022. Key findings included over 1,500 documented instances of 'phantom braking'—where the vehicle brakes without an apparent obstacle—and over 2,400 reports of unintended acceleration. More critically, the documents revealed a corporate communication protocol instructing employees to handle Autopilot failure discussions verbally, specifically to avoid creating a written paper trail that could be used in class-action lawsuits. The leak also highlighted internal logs concerning a fatal crash involving the experimental FSD Beta software, which had reportedly been scrubbed from public safety reports, suggesting a systemic effort to manage public perception of the technology's safety record.
02Background
As Tesla aggressively marketed its Autopilot and FSD capabilities, public and regulatory scrutiny regarding the system's reliability increased significantly. Concerns mounted over whether the technology was adequately tested and if the company was transparent about its limitations. The leak occurred during a period of heightened regulatory interest, particularly from the National Highway Traffic Safety Administration (NHTSA), regarding autonomous vehicle safety.
03Key revelations
- 01The existence of over 2,400 documented instances of unintended acceleration, which the company internally minimized by blaming 'driver error'.
- 02The internal directive to employees to avoid written communication regarding Autopilot failures to limit legal exposure.
- 03The existence of internal logs detailing a fatal crash involving FSD Beta that was allegedly removed from public safety reports.
04Technical analysis
The leaked data provided raw customer complaint logs and internal engineering notes. The analysis focused on identifying patterns in system failures, such as the discrepancy between reported 'phantom braking' incidents and the company's internal advice to classify them as mere 'calibration events.' The logs also contained details on the software's operational parameters and failure modes, suggesting that the system's failure was often attributed to 'driver error' even when internal data suggested otherwise.
- Attack method
- Data Exfiltration / Whistleblowing
05Threat actor
Aliases
- Internal Sources
- Service Database Personnel
Attribution sources
- Handelsblatt
- Investigative Journalism
06Victims and impact
Additional victims
- NHTSA
- General Public/Customers
Countries affected
- USA
07Data exposed
Data types
- Safety Complaint Logs
- Engineering Notes
- Customer PII (implied)
- Operational Data
Notable documents
- Customer Safety Complaint Logs (2015-2022)
- FSD Beta Crash Logs
08Financial damage
Damage estimate is speculative, relating to potential class-action lawsuits and regulatory fines.
09Timeline
- 2015-01-01Start of documented safety complaint period (2015-2022).
- 2023-05-25Leak of the 100GB internal dataset to the press.
10On the record
Employees are instructed to avoid written communication regarding Autopilot failures to minimize discovery in potential class-action lawsuits.
11Reaction and fallout
Public reaction
The leak triggered immediate public outcry and intense media scrutiny, raising global concerns about the safety and regulatory oversight of autonomous vehicle technology. Consumer trust in Tesla's self-driving claims was significantly challenged.
Political impact
The incident intensified regulatory pressure on Tesla and the entire autonomous vehicle industry, prompting calls for stricter federal oversight from bodies like the NHTSA and Congress.
12Legal
The leak is expected to fuel multiple class-action lawsuits and regulatory investigations into Tesla's safety reporting practices and the true capabilities of its FSD technology.
Civil lawsuits
- Potential class-action lawsuits regarding product liability and safety misrepresentation.
13Aftermath
Policy changes
- Increased calls for mandatory, standardized federal safety reporting for autonomous vehicles.
Regulatory changes
- Heightened scrutiny and potential revision of NHTSA guidelines for ADAS (Advanced Driver-Assistance Systems).
Security improvements
- Increased industry focus on verifiable, standardized data logging and transparency in autonomous vehicle development.
14Significance and legacy
Significance
This leak represents a critical moment in the history of autonomous vehicle development, shifting the narrative from technological capability to corporate accountability. It established a precedent for using internal corporate documents to challenge industry hype and regulatory self-reporting, forcing a public reckoning with the gap between marketing claims and documented engineering reality.
Legacy
The Tesla Files have permanently elevated the standard for transparency in the automotive tech sector. They ensure that future regulatory bodies and legal actions will scrutinize internal communications and raw data logs, making it significantly harder for corporations to manage public perception by suppressing negative internal findings.
15Disclosure and media
- Authentication
- Source reporting and internal consistency checks
Media partners
- Handelsblatt
Publishing organisations
- Handelsblatt
17Field notes
- 01The leaked documents contained specific internal instructions to classify serious system failures as minor 'calibration events' to mitigate legal risk.
- 02The sheer volume of the data (100GB) suggests a comprehensive, long-term data retention policy for customer complaints, far exceeding typical public reporting.
18Resolution
The leak remains a key reference point in ongoing legal and regulatory investigations, maintaining pressure on Tesla to provide full transparency regarding its safety data and software limitations.
19Sources
Official documents
- NHTSA Investigation Reports (Ongoing)
References
- [1]Handelsblatt Leak
- [2]Tesla Service Database Logs









