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.”

Advertisement

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. 

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. 

Advertisement

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

Tesla enters two new markets on two different continents in one week

Published

on

Tesla entered two new markets this week by advancing its presence in Latvia (Europe) and officially launching operations in Uruguay (South America), marking a rapid dual-continent expansion.

These moves underscore the company’s strategy to tap into emerging EV markets with supportive policies, renewable energy grids, and growing demand for sustainable transport.

Latvia: Strengthening the Baltic Footprint

In Latvia, Tesla has built on its earlier registration of Tesla Latvia SIA in late 2025 with recent steps toward full operations, including job postings for a service center and representation in Riga. This aligns with broader Baltic expansion following Lithuania’s model of pop-up stores and service centers.

EV penetration in Latvia stands at around 7 percent for BEVs in new passenger car registrations. 2025 data showed 1,602 BEVs out of about 22,500 total, or 7.1 percent, with combined plug-ins nearing 19 percent. Growth has been steady but below the European average, supported by government subsidies and infrastructure development. Tesla models like the Model 3 lead local EV registrations.

Vehicles for the Latvian market will likely be sourced from Gigafactory Berlin or Gigafactory Shanghai. Charging infrastructure is robust for the region as well, with over 400- 2,000 public points, with Tesla Superchargers in Riga, Jūrmala, and along Via Baltica routes offering up to 250 kW.

Uruguay: Third South American Country

Tesla teased its Uruguay arrival with “Estamos llegando,” or, “We are arriving,” on social media, followed by an official presentation scheduled for mid-July.

The company established Tesla Uruguay SAS, homologated Model 3 and Model Y (three versions each), and appointed local leadership. This makes Uruguay Tesla’s third official South American market after Chile and Colombia.

Uruguay boasts one of Latin America’s highest EV penetrations, with battery-electric vehicles exceeding 20 percent market share recently, driven by tax incentives, high fuel prices, and a nearly 95-100 percent renewable electricity grid. Hundreds of Teslas already operate via grey imports, but official sales bring warranties, service, and support.

Vehicles will be imported from Gigafactory Shanghai, enabling competitive pricing for Model 3 and Model Y. Charging plans include Supercharger development alongside existing infrastructure, leveraging the country’s green energy advantage for affordable operation.

Tesla Superchargers follow Model 3 and Model Y to South American country

Tesla’s Dual Continent Expansion

Tesla’s simultaneous push into Latvia and Uruguay demonstrates efficient scaling: prioritizing service and infrastructure first, then direct sales in high-potential niches. In Europe, it fills Baltic gaps; in Latin America, it counters Chinese dominance while leveraging renewables.

This dual move signals Tesla’s ambition to accelerate global EV adoption amid varying regional paces. By addressing local needs, like subsidies in Latvia or incentives and green grids in Uruguay, Tesla not only boosts volumes but advances its mission of sustainable energy.

For investors and consumers, it highlights resilience and opportunity in diverse markets, potentially paving the way for further growth in underserved regions. With strong fundamentals in both, these entries could yield long-term gains as EV transitions mature worldwide.

Continue Reading

Elon Musk

SpaceX announces new Starship 13 test flight target date

Published

on

SpaceX Starship V3 flight 12
SpaceX Starship V3 flight 12 (Credit: SpaceX)

SpaceX has announced a new target date for the thirteenth test flight of Starship: Monday, July 20, with the launch window opening at 6:45 p.m ET/5:45 p.m. CT.

This is the first rescheduling attempt of Starship’s 13th test flight. It was set to launch last night, but SpaceX scrubbed the launch attempt.

CEO Elon Musk revealed that some of the engines on Starship did not start, which automatically triggers a launch abort. Two of the Raptor engines will be removed and replaced.

SpaceX officially announced the new launch window this morning.

Starship’s 13th test launch comes with a few new objectives, but SpaceX does not plan to attempt a catch of the booster, which it has done several times in the past.

For Starship’s Upper Stage, there are some adjustments to ensure engine reusability that will be assessed during the ascent, and 20 operational Starlink V3 satellites are also set to make their way into space. SpaceX also plans to attempt an in-space relight of a single Raptor engine, which is a critical demonstration for future orbital deorbit, refueling, and deep space maneuvers.

Ultimately, it will splash down in the Indian Ocean.

The continuous tests help SpaceX advance the Starship program toward eventual full reusability, operational Starlink V3 deployment, and future missions, which include NASA’s Artemis program.

Continue Reading

Elon Musk

SpaceX Starship Flight 13 aborted at Zero and Musk just told us what broke

Four Raptor engines failed to ignite at T-zero, forcing SpaceX to scrub Starship Flight 13 Thursday.

Published

on

By

SpaceX scrubbed the Starship Flight 13 launch attempt Thursday evening at the last possible moment, after four of the Super Heavy booster’s 33 Raptor 3 engines failed to ignite during the startup sequence. The 90-minute window had opened at 6:45 p.m. EDT from Starbase in Boca Chica, Texas, and the countdown had proceeded without issue all day, with more than 11.5 million pounds of liquid methane and liquid oxygen being fully loaded into the rocket before the automated abort triggered. SpaceX’s launch directors posted on X, “Standing down from today’s flight test attempt,” and shut down the livestream shortly after.

Musk confirmed the root cause within hours. “Some of the engines didn’t start, triggering an automatic launch abort,” he wrote on X. “To be confident of a good flight, 2 Raptors will be removed and replaced. Most probable launch timing is early next week.” SpaceX engineers began draining propellant tanks immediately and Booster 20 was rolled back to its hangar for inspection.

SpaceX comes with a slew of changes for Starship Flight 13

 

The timing adds a layer of significance that did not exist during any of the previous 12 Starship flights. This is the first time SpaceX has attempted to launch Starship since the company made its stock market debut in June, listing under ticker SPCX at $135 per share. Public investors are now watching every Starship outcome in real time, and a last-second abort carries more visibility than it would have six months ago.

Flight 13 was designed to be one of the most consequential tests in the program’s history. It was set to carry 20 Starlink V3 satellites, the first operational payload Starship has ever attempted to deploy. Six of those satellites carried external cameras to photograph Starship’s heat shield from the outside during flight, which would act as a self-inspection approach SpaceX has never attempted before. The mission also needed to complete a Raptor engine relight in space, a step SpaceX skipped on Flight 12 in May after losing an engine during ascent. That Flight 12 booster also flipped 90 degrees off course during its boostback burn when five engines failed to reignite.

SpaceX has not announced an official next launch date. Musk’s “early next week” window points to July 21 or 22 at the earliest, pending the engine swap and a return to the pad.

Continue Reading