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

Investor's Corner

Tesla opens the Q&A for its biggest earnings call yet

Tesla opens its Q3 earnings Q&A, and Cybercab, Robotaxi, Optimus and regulators loom over October 21.

Published

on

By

Tesla has opened its shareholder question portal for the Q3 2026 earnings call, with the Say Q&A page already listing questions. Investors have until 4:00 p.m. EDT on October 20 to submit and vote on what management should answer.

The call is set for Wednesday, October 21. Tesla will post results after the market closes, with a live webcast at 4:30 p.m. CT, or 5:30 p.m. ET, through its investor relations site.

Say ranks questions by the number of shares behind the votes, which gives institutional holders extra weight over the retail crowd.

Ahead of Q2, retail investors asked why Robotaxi growth had stalled, when Cybercab would start customer rides, and where the Optimus Gen 3 ramp stood, while an institutional holder asked how Tesla and SpaceX would split Terafab duties. Cybercab has since answered one of those. Tesla said last week it has 300 plus Cybercabs serving Austin, up eightfold in 30 days, with Dallas named as the next city. The questions now are likely to move from when to how fast.

There is also a regulatory question hanging over the call. NHTSA has demanded sworn answers on how the pedal free Cybercab was certified against federal safety standards, with responses due October 30, nine days after the call. Whether an analyst raises it live is unknown, but it is the kind of exposure that tends to find its way into a Q&A.

The numbers will not be the main draw. Tesla already reported 486,532 deliveries and 13.7 GWh of storage for the quarter. Consensus sits around 43 to 45 cents per share on roughly $27.8 billion in revenue, according to Zacks, after a Q2 report that missed on EPS. Goldman Sachs, which holds a Neutral rating and a $360 target, argues the outlook for Robotaxi, FSD and Optimus will matter more to the stock than the quarter itself.

The call also lands six days after the rescheduled Roadster event, which Tesla will stream on X on Thursday, October 15, at 7:55 p.m. CT. If the Roadster shows up with a production date or a SpaceX thruster package, expect it to climb the voting list before the deadline.

Continue Reading

Elon Musk

Ukraine says Starlink is cutting out its military drones as Poland calls out Elon Musk

Ukrainian officials allege SpaceX limited military Starlink speeds, disrupting drone missions; SpaceX has not commented.

Published

on

By

Credit: Mykhailo Fedorov/Twitter

Ukrainian officials are accusing SpaceX of placing a speed limit on the military version of Starlink that their forces use to fly drones, but SpaceX has not confirmed that any change was made. Presidential adviser Serhiy Beskrestnov said in a Telegram post on Wednesday that Starshield terminals have begun losing service when they move faster than about 100 miles per hour, according to a Reuters report. “Our defense forces did not receive a warning about this limitation, and this led to the disruption of several missions,” he wrote.

Ukraine’s 7th Rapid Reaction Corps told Reuters that connections dropped for 10 to 20 seconds at just 68 to 75 mph, which made the drones harder to control. Volunteer Serhiy Sternenko, citing military reports, said the dropouts are now starting at 37 to 43 mph. These accounts come from Ukrainian officials and military sources and have not been independently verified. Regular civilian terminals were reportedly not affected, according to EUalive.


SpaceX has not publicly commented or explained what, if anything, changed. Beskrestnov and other Ukrainian officials believe the issue is intentional and point to the timing. Washington has been pressing Kyiv to stop long range strikes on Russian oil refineries after President Trump called for an “energy ceasefire,” and Musk posted on Saturday that “Zelensky has gone too far.” EUalive noted that neither Ukrainian nor Polish officials have presented evidence that the limit was ordered by Washington or by SpaceX, so the link to politics remains an allegation. Other explanations, such as a technical or policy change affecting fast moving terminals, have not been ruled out.

Poland’s foreign minister, Radosław Sikorski, responded on X by quote tweeting a Kyiv Independent report and writing: “Hey, @elonmusk, big man, are you playing politics with your products again? As your European customers, we are watching you.” Poland is the largest funder of Ukraine’s Starlink service, having supplied more than 29,000 terminals and covering operating costs Sikorski has put at roughly $50 million a year. The wording echoes their 2025 clash, when Musk told Sikorski to “be quiet, small man.” At the time of writing, neither Musk nor SpaceX had responded to the claims.

The dispute sits on top of a long history. Musk confirmed in February 2022 that Starlink was active in Ukraine after a request from a Ukrainian minister. That October, SpaceX asked the Pentagon to share the bill and Musk said the cost was approaching $20 million a month, before he reversed course and said SpaceX would keep paying. In December 2024 the Pentagon moved some of those terminals onto the Starshield service, the government version now at the center of the complaints.

SpaceX has also changed how its network treats certain terminals in Ukraine before, and that time it was with Kyiv’s cooperation. In February, Ukrainian officials confirmed that terminals believed to be used by Russian troops were disabled after coordination with SpaceX, a step that Ukrainian commanders later said hurt Russian assaults. Whether anything similar is behind the latest reports is unclear, which is why Kyiv is asking for answers.

Ukraine is already looking at backups. Defense tech company Stetman is developing its own satellite system, UASAT-NANO, and officials in Europe have discussed alternatives to Starlink since early 2025, though none match its scale yet.

Continue Reading

Elon Musk

FAA kicks off review of SpaceX’s bid to fly Starship nearly every day

FAA is reviewing SpaceX’s plan for 456 Starship launches a year, up from 25 today.

Published

on

By

Rendering of Elon Musk overlooking a Starship fleet (Credit: Grok)

The FAA said Tuesday that it will prepare an environmental impact statement on SpaceX’s proposal to run as many as 456 Starship launches and 912 landings a year from Starbase, Texas. SpaceX is currently authorized for 25 launches and 50 landings annually, which makes the request roughly 18 times the existing ceiling. The notice of intent is set to publish in the Federal Register on Wednesday.

The plan comes in two phases. Phase 1 would allow up to 100 launches and 200 landings a year, on any day and at any hour. Phase 2, which the FAA says could arrive within several years, would raise the limit to the full 456 launches, still at any hour but only on weekdays. The agency noted that 912 landings is the upper limit for the Texas facility no matter where a given mission begins, and that Starship and Super Heavy could come down at the launch site or in the Gulf and open ocean.

A draft statement will be released for public comment at a later date, and the FAA has not said when. According to the Federal Registar, written comments are due November 30 on regulations.gov under docket FAA-2026-12808, with in person scoping meetings on November 17 in Brownsville and November 19 in Port Isabel, plus a virtual session on November 18. The review will weigh air quality, wildlife, coastal resources, water, noise, and aviation, and the FAA said any increase beyond this proposal would need its own separate review.

The numbers look large next to what Starbase has actually done. Starship has flown three times from Texas this year, including Flight 14 on September 28, the first orbital flight, which deployed 26 Starlink V3 satellites. Bloomberg reported that Starbase has never launched more than five times in a calendar year. The current cap of 25 comes from an FAA approval in May 2025. In February, the agency also approved up to 44 Starship launches a year from Launch Complex 39A in Florida, so Phase 1 in Texas alone would more than double that allowance.

Musk has said Starship could eventually fly more than once per hour within less than a decade, per Bloomberg. The nearer term target is Flight 15. Musk said on October 10 that it is hopefully four to six weeks away and will try to catch the ship with the tower, as Teslarati covered. That flight still runs under the existing 25 launch limit, and so would every Starbase launch for as long as the new review takes.

As of mid morning Pacific time on Tuesday, SpaceX had not posted about the filing on its own account.

Continue Reading