Tesla has begun remotely shutting off Full Self-Driving software on vehicles where owners obtained the feature through unauthorized hacks, according to a report published by Electrek on April 17, 2025. The move, which Tesla has not publicly confirmed, would mark one of the most aggressive uses of over-the-air control by any automaker and arrives as federal and state regulators are already scrutinizing FSD over crash investigations, alleged traffic violations, and marketing claims.
FSD currently costs $99 per month as a subscription or can be purchased outright for $8,000. Owners who obtained it through official channels are not reported to be affected. But for a small community of hackers who found ways to unlock the feature without paying, the reported crackdown signals that Tesla is willing to reach into vehicles after the sale to enforce its software licensing.
What regulators are already doing
The reported disabling lands in the middle of an already tense regulatory environment for Tesla’s self-driving ambitions. Several of the regulatory actions described below predate the April 2025 report but remain relevant because the investigations are ongoing and form the backdrop against which any crackdown on hacked FSD would occur.
The National Highway Traffic Safety Administration opened a formal investigation into FSD after a string of crashes involving vehicles running the software. That probe, first announced in 2022 and expanded in subsequent years, has examined incidents in which cars operating under FSD reportedly ran red lights and drove on the wrong side of the road. NHTSA has since granted Tesla additional time to respond to the agency’s inquiries, according to the AP’s reporting on the probe, a sign the investigation is growing more complex rather than winding down. The specific deadline extension has not been tied to a publicly available filing date in the reporting reviewed for this article.
A separate but related NHTSA inquiry, also documented in AP reporting from prior years, is focused specifically on alleged traffic-law violations committed by vehicles using FSD. That investigation involves formal agency correspondence and could lead to a recall or mandatory software changes.
At the state level, California’s Department of Motor Vehicles threatened Tesla with a 30-day suspension of its dealer license over what the agency called deceptive self-driving claims in Autopilot and FSD marketing. That action, first reported in 2022, targeted the gap between how Tesla describes the technology to buyers and what the software can actually do. The DMV complaint has not resulted in a license revocation as of this writing, but it remains part of the broader regulatory record.
Together, these actions from multiple government bodies form a clear pattern: regulators have been questioning both FSD’s real-world safety record and the accuracy of Tesla’s public statements about it for years. Any crackdown on unauthorized FSD installations would unfold against that backdrop.
What we still don’t know
Key details about the reported remote disabling remain thin. Tesla has not issued a statement, and neither NHTSA nor any other agency has commented. The number of vehicles affected, the geographic scope, and the technical method Tesla used to detect hacked installations have not been disclosed. The Electrek report does not name specific vehicle models, individual owners, or the precise date the disabling began, leaving the timeline anchored only to mid-April 2025.
The nature of the hack itself is also unclear. Whether owners gained access through a software exploit, a hardware modification, or some combination has not been detailed in any verified source. The Electrek report references the broader Tesla hacking community but does not identify a specific group, tool, or vulnerability by name. That distinction matters: a software-only vulnerability could theoretically be patched with a single over-the-air update, while hardware tampering would be harder to detect remotely and could raise separate warranty and safety concerns.
Tesla’s motivation is another open question. The company could be acting to protect safety by keeping unvetted code off public roads, to defend its subscription revenue, or to demonstrate control over its software ecosystem at a moment when regulators are watching closely. Those explanations are not mutually exclusive, and without a public statement from Tesla, pinning down a single motive would be guesswork.
Elon Musk has repeatedly promoted FSD on his social media accounts. In an April 2025 post on X, he described FSD as improving “exponentially” and predicted fully autonomous driving would arrive soon. Those public claims are part of what regulators have scrutinized, but Tesla has not commented on how they relate to the reported crackdown on hacked access.
The legal gray zone of remote control
Automakers have broad authority to push over-the-air updates, especially when framed as safety fixes or recalls. Tesla has used that power repeatedly, adjusting battery range, adding features, and issuing software-based recalls without requiring a service visit.
But remotely removing a feature raises a different set of questions. An owner who purchased FSD outright for $8,000 and later had it disabled could argue the company took away something they paid for. Tesla’s terms of service almost certainly reserve the right to modify or revoke software access, but those provisions have not been tested in court in a scenario quite like this one. No court ruling or regulatory guidance specifically addressing the remote disabling of a hacked driver-assistance feature has surfaced in public records.
Consumer-rights advocates have long warned that software-defined products blur the line between ownership and licensing. Cars have historically been among the most tangible things a person can own, but when core capabilities depend on cloud-side permissions and ongoing manufacturer authorization, the traditional concept of ownership starts to erode. The reported FSD crackdown, if confirmed, would be one of the starkest examples yet.
What this means for current and prospective FSD buyers
For drivers who bought FSD through official channels, nothing changes based on what has been reported so far. But the episode is a reminder of how much control Tesla retains over its vehicles after they leave the lot. Even when the hardware is fully owned, access to key software features can hinge on terms of service that the company can update at any time.
For the enthusiast and hacking communities that have long treated cars as objects to be modified and improved, the landscape is shifting. Code, not hardware, increasingly defines what a vehicle can do, and the original manufacturer can intervene from thousands of miles away.
Regulators have not weighed in on the specific question of remote feature disabling, but the active federal and state investigations into FSD suggest the broader issue of software control is already on their radar. As agencies probe how FSD performs in real traffic and whether Tesla’s marketing matches reality, questions about who ultimately controls the software, and under what conditions it can be withdrawn, are only going to get louder.
Tesla’s next public move will shape how this story is remembered: as a narrow anti-piracy measure or as an early precedent in the growing fight over who really controls a modern car.
More from Morning Overview
*This article was researched with the help of AI, with human editors creating the final content.
