Connect with us

News

Tesla employee foregoes $1M payment, works with FBI to thwart cybersecurity attack

Tesla Gigafactory 1, where Model 3 battery cells are produced. (Photo: Tesla)

Published

on

Sometimes, the events that transpire inside a company could be just as exciting and nail-biting as the most popular thrillers in fiction. In Tesla’s case, such a scenario recently played out, as a worker in Gigafactory Nevada ended up turning down a $1 million incentive, working closely with the FBI, and thwarting a planned cybersecurity attack against the electric car maker. 

This Tuesday, the Department of Justice announced the arrest of Egor Igorevich Kriuchkov, a Russian citizen accused of conspiring to breach the network of a US company and introduce malware to compromise the said company’s networks. Media reports about the incident have identified the US company to be electric car maker Tesla. Interestingly enough, a criminal complaint filed by the FBI Las Vegas Field Office suggests that the attempted cybersecurity attack is no ordinary hacking attempt — it may very well be part of a well-financed, organized, scheme. 

The plan begins

The remarkable story began when a Russian-speaking, non-US citizen working at Tesla’s Gigafactory Nevada was contacted by Kriuchkov. The employee, whose identity has not been revealed, has access to the electric car maker’s computer networks. On July 16, the Russian citizen contacted the Giga Nevada employee through WhatsApp asking to meet with him in Sparks, Nevada. As noted in a report from Clearance Jobs, the fact that Kriuchkov approached a Russian-speaking, non-US citizen working at Gigafactory Nevada suggests that the team behind the cyberattack attempt has done their research well. 

The Tesla employee, some colleagues, and Kriuchkov met socially from August 1-3, which included a trip to Lake Tahoe. Interestingly enough, Kriuchkov reportedly declined to be present in any photos that were taken during the trip. At one point when the group was taking a photo during a picturesque sunset, Kriuchkov reportedly remarked that he would “just remember the beauty of the sunset and did not need a photograph.” After the relatively harmless Lake Tahoe trip, the Russian citizen asked the Tesla employee to meet with him for some “business.”

Down to “business”

During their “business” meeting, Kriuchkov revealed his hand. The plan involved the Tesla employee inserting malware provided by Kriuchkov and his associates to the electric car maker’s systems. After the malware is inserted, a distributed denial of service (DDoS) attack would occur that could allow the hackers to occupy the Tesla information security team. The malware would also allow the hackers to extract corporate and network data, which would be held ransom until the electric car maker pays up. For his participation in the ploy, the Gigafactory Nevada employee would receive $500,000, later raised to $1 million, to be paid in cash or bitcoin. 

Unfortunately for Kriuchkov and his team, the Giga Nevada employee actually reported the planned cybersecurity attack to Tesla, which, in turn, contacted the FBI. The FBI stepped in, and with the agency’s help, the Tesla employee continued to communicate with Kriuchkov, trying to get as much information as possible about the hackers’ processes, procedures, and infrastructure. The efforts proved fruitful. In one conversation, the hacker reportedly boasted that his team had recently received a ransom worth over $4 million from a high profile company. Later reports would reveal that the company in question was CWT Travel, which reportedly paid a ransom of $4.5 million. 

Advertisement
-

The plan falls through

During a meeting on August 19, the Tesla employee, wearing a wire from the FBI, met with Kriuchkov. The hacker agreed to pay an advance of $11,000 to the Giga Nevada worker. Two days later, on August 21, the Tesla employee was contacted by the hacker once more, who stated that the project was being “delayed” and all payments relating to the plan would not be transferred until a later date. Kriuchkov also informed the Tesla employee that he was leaving the area the following day. Behind the scenes, the FBI was able to get in touch with the hacker, who, in turn, drove overnight from Reno, Nevada to Los Angeles in what appeared to be an attempt to flee the United States. 

Kriuchkov was unsuccessful, as he was arrested on August 22, 2020 in Los Angeles. The hacker is currently being detained pending trial. Fortunately for Tesla, the company was able to get away from what could have been a serious cybersecurity attack, and it has one employee to thank for it. It takes a lot, after all, to say no to a $1 million reward, as others have compromised far more for far less. 

Read the FBI’s complaint against Kriuchkov below. 

Complaint Egor Kriuchkov 3 20 Mj 83-0-0 by Simon Alvarez on Scribd

Advertisement
-

Simon is an experienced automotive reporter with a passion for electric cars and clean energy. Fascinated by the world envisioned by Elon Musk, he hopes to make it to Mars (at least as a tourist) someday. For stories or tips--or even to just say a simple hello--send a message to his email, simon@teslarati.com or his handle on X, @ResidentSponge.

Advertisement
Comments

News

SpaceX completes another secret Pentagon launch, adding to suspected Starshield buildout

SpaceX launched the classified USSF-385 mission from Vandenberg, landing its booster on a tenth flight.

Published

on

By

US Golden Dome space defense system (Concept render by Grok)

SpaceX launched another classified mission for the U.S. Space Force from California early Saturday morning, and the Falcon 9 booster that carried it landed on a drone ship in the Pacific for the tenth time. The USSF-385 mission lifted off from Space Launch Complex 4E at Vandenberg Space Force Base at 7:00 a.m. PT.

Booster B1100 touched down on Of Course I Still Love You roughly eight and a half minutes after liftoff. It was the booster’s tenth flight and tenth successful landing, following the NROL-95 national security mission and eight Starlink launches. Its previous flight, a Starlink Group 15 mission on August 22, came just 35 days earlier. SpaceX ended its livestream shortly after the landing, which is standard for classified payloads, and neither the company nor the Space Force has said what the rocket carried.

USSF-385 is the fourth Space Force launch from the same Vandenberg pad in roughly six weeks, following USSF-366 on August 15, USSF-153 on September 10, and USSF-259 on September 17. When SpaceX flew USSF-366 in August, independent trackers noted that the rocket’s stage drop zones matched SpaceX’s Starlink Group 15 missions, pointing to Starshield, the government version of the Starlink satellite bus. The Space Force later cataloged 23 satellites after both USSF-366 and USSF-153, while USSF-259 placed 17 satellites into a different orbital plane, per KeepTrack. Launch databases describe USSF-385 the same way, though the payload remains officially unidentified.

Starlink’s Starshield wins contract with US Space Force

The cadence lines up with the contracts, because in July, the Space Force awarded SpaceX $1.6 billion in task orders for 18 Falcon 9 missions from Vandenberg through the end of 2027. SpaceX also holds contracts to build pieces of that same network, which pushed its Pentagon contract total for 2026 past $8 billion.

Saturday’s flight was also the sixth and final Falcon 9 launch from Vandenberg in September, according to Spaceflight Now, while only one Falcon 9 flew from the East Coast this month as SpaceX shifts its Florida infrastructure toward Starship. Launch trackers list it as SpaceX’s 112th mission of 2026 and the 108th Falcon 9 flight of the year, with SLC-4E turned around about six and a half days after its previous launch.

The West Coast pad will not stay quiet for long, considering SpaceX has another Starlink mission scheduled from SLC-4E on September 30. Meanwhile, in Texas, the company is two days away from Starship Flight 14, which is targeting Monday at 7:15 a.m. CT for the vehicle’s first attempt to reach orbit.

Continue Reading

News

Tesla hints at new Roadster design in surprise clip

Tesla ended its Semi event with a Roadster teaser revealing a new front light bar.

Published

on

By

Tesla Battery Day event (Credit: Ryan McCaffrey/Twitter)

Tesla closed out its Semi event in Nevada on Thursday night with a nod to its own history, dropping a short Roadster teaser that suggests the production car will look noticeably different from the prototype first shown in 2017.

“We can’t have a Semi event without the Roadster,” Tesla engineering executive Lars Moravy told the crowd before the clip played. The line was a deliberate callback. Tesla first revealed the next generation Roadster in November 2017 by driving it out of the back of a Semi trailer at the truck’s original unveiling in Hawthorne, California.

The new video opens on trailer doors swinging apart in the dark. A thin white light bar glows across what appears to be the nose of the car, Tesla and SpaceX logos flash over the frame, and the Roadster name appears before the clip ends on “See you next week.” Tesla posted the nine second clip on X after the livestream wrapped.

The light bar is the most concrete design detail so far. The 2017 prototype used two separate curved headlamp pods, while a connected front light strip would bring the Roadster in line with the Cybertruck, Cybercab, Semi, and refreshed Model Y. Sawyer Merritt was among the first to point out what looked like part of a SpaceX logo in the video, something Tesla has not addressed.

That logo fits the buildup around the optional SpaceX Package, which Elon Musk has long said would use cold gas thrusters to improve acceleration and possibly allow the car to briefly leave the ground. Tesla’s “Go for launch” post on September 12 set the October 1 date, and invitations sent to reservation holders place the event in Waco, Texas, at 8:30 p.m. Eastern. Waco sits roughly 20 minutes from SpaceX’s McGregor rocket test site, where the FAA has put a temporary flight restriction in place from September 18 through October 2, covering a 1.5 nautical mile radius from the surface up to 10,000 feet.

Tesla is also taking money ahead of the reveal. The company reopened Roadster reservations earlier this week with a $5,000 refundable card payment, followed by a $45,000 wire transfer due within 10 days. That puts buyers at $50,000 committed before Tesla has published a price.

The original pitch set a high bar: 0 to 60 mph in 1.9 seconds before any upgrades, 620 miles of range, a top speed above 250 mph, and production in 2020. That timeline has slipped repeatedly, and Tesla has since pointed to production at Gigafactory Texas no earlier than 2027. The company has said next Thursday’s event will include pricing, specifications, and production targets, the three details original reservation holders have been waiting on for nearly nine years.

Continue Reading

News

Tesla Full Self-Driving release in the EU gets delayed

Published

on

Credit: Grok Imagine

Tesla Full Self-Driving’s release in Europe is set to be delayed by at least a few months.

The European Union will not vote on Tesla’s Full Self-Driving (Supervised) on October 6. The draft agenda for the 119th meeting of the Technical Committee on Motor Vehicles lists only a 25-minute “continuation of discussions” on the Netherlands’ Article 39 request, not a decision. The next scheduled TCMV session is in December, which is now the earliest date a bloc-wide vote could occur.

Tesla Europe had pointed to October 6 as a possible EU-wide vote after the Dutch vehicle authority RDW granted the first European type approval on April 10.

That approval, under UN Regulation 171 plus an Article 39 exemption in EU Regulation 2018/858, is the legal file other member states have been recognizing one by one. The same committee has already discussed the request twice without voting.

Elon Musk’s reply to the delay was a single word: “Sigh.”

Seven EU countries have now cleared FSD Supervised on their own roads: the Netherlands, Lithuania, Estonia, Denmark, Belgium, Slovenia, and Czechia. Those seven states represent about 53 million people, or roughly 12 percent of the EU population. An EU-wide authorization still needs a qualified majority: at least 15 of 27 member states representing 65 percent of the bloc’s population, about 292 million people.

Germany, France, Italy, and Spain remain the decisive markets. France has already rejected the current system; several other governments have flagged speed-limit compliance as the main sticking point.

The safety case Tesla is putting in front of those governments is now public. On September 1, Tesla Europe said FSD Supervised was in use by more than 70,000 customers, covering over 1 million kilometers a day, and was 4.1 times less likely to be involved in a crash than manual driving across 100 million kilometers on EU public roads.

An earlier mid-year cut of the same fleet data, covering 65 million kilometers in five approved countries, put the collision advantage at 5.2 times, with zero highway collisions over 41.9 million kilometers. Tesla also reported far fewer automatic emergency braking events, harsh accelerations, and hard swerves than in comparable manual Tesla driving. Those figures are company-reported, not independently audited.

Tesla Full Self-Driving is taking over Europe: fourth country gets FSD approval

The public-health backdrop is harder to dispute. European countries recorded about 19,400 road deaths in 2025, or roughly 53 a day, most of them attributed to human error. FSD Supervised is not unsupervised autonomy; the driver remains legally responsible. But the software is already legal and in daily use across seven member states.

Until TCMV votes, the rest of the EU remains a patchwork: available in Prague and Amsterdam, locked behind review in Paris and Berlin. December is now the next chance to close that gap.

Continue Reading