Russian hackers executed the 2025 cyberattack on Jaguar Land Rover, causing an estimated £1.9 billion ($2.5 billion) in economic damage—the most expensive cyberattack in UK history. The breach began August 31, 2025 through a vishing campaign targeting JLR's IT helpdesk.

Create a landscape editorial hero image for this Studio Global article: Search & fact-check with cited sources for What specific Russian hacking group was responsible for the 2025 cyberattack on Jaguar Land Rover. Article summary: ## Attribution and Key Findings in the Jaguar Land Rover Cyberattack. Topic tags: general, news, general web, user generated, government. Style: premium digital editorial illustration, source-backed research mood, clean composition, high detail, modern web publication hero. Use reference image context only for broad subject, composition, and topical grounding; do not copy the exact image. Avoid: logos, brand marks, copyrighted characters, real person likenesses, fake screenshots, UI text, readable text, watermarks, charts with fake numbers, clickbait thumbnails, icons, and tiny thumbnail layouts. Make it useful as an illustrative visual, not as factual evidence
A phone call, not an exploit, shut down one of the UK's largest manufacturers. The 2025 cyberattack on Jaguar Land Rover began with a vishing (voice phishing) campaign on August 31 and escalated into a five-week production halt that cost the British economy an estimated £1.9 billion ($2.5 billion) . While investigators from UK and US law enforcement agencies have concluded the attack was carried out by Russian hackers, the specific operational unit—such as APT29/Cozy Bear, Sandworm, or Star Blizzard—has not been publicly named as of the most detailed reporting in June 2026
. Authorities are still working to determine whether the attackers operated under Kremlin direction or with its tacit assent
.
The breach relied on social engineering rather than sophisticated technical exploits . Attackers launched a high-context helpdesk vishing campaign, calling JLR's IT service desk—reportedly targeting an employee at its IT service provider, Tata Consultancy Services
. Posing as legitimate employees, they requested credential resets and multi-factor authentication re-registrations, enabling token theft and login with stolen credentials
.
Once inside, attackers moved laterally from IT systems to ERP/MES (enterprise resource planning and manufacturing execution systems), ultimately disrupting production lines on the shop floor . The intrusion was detected on August 31, and JLR paused production on September 1. It took nearly six weeks to begin restarting manufacturing, costing the company an estimated £50 million per week in direct losses
.
Immediately after the attack, a group calling itself Scattered Lapsus$ Hunters claimed responsibility on Telegram . The name suggested collaboration between Scattered Spider, Lapsus$, and ShinyHunters—three English-speaking cybercrime groups
.
But investigators later concluded this claim was false. The attack was different in methodology and motivation from typical criminal ransomware: there was never a demand for money, and the intent appeared to be sabotage rather than extortion . The attackers used "Scattered Lapsus$ Hunters" as a cover identity, and the initial attribution to that group by some news outlets was incorrect
.
The investigation was led by law enforcement agencies and private cybersecurity firms from both the United Kingdom and the United States . The National Cyber Security Centre (NCSC), which sits inside GCHQ, led the technical and forensic aspects of the investigation, with support from UK and U.S. national security agencies
. The New York Times reported the conclusions based on five anonymous sources familiar with the investigation
.
The Cyber Monitoring Centre (CMC), an independent UK body, categorized the incident as a Category 3 systemic event on its five-point scale and estimated the total UK economic impact at £1.9 billion (approximately $2.5 billion), affecting over 5,000 businesses .
On September 27–29, 2025, Business Secretary Peter Kyle announced the UK government would back a £1.5 billion ($2 billion) loan guarantee from a commercial bank for Jaguar Land Rover . The unprecedented intervention was designed to stabilize JLR's finances, protect skilled jobs, and secure its supply chain, which faced collapse due to delayed payments
. The guarantee was described as an emergency measure to prevent thousands of layoffs across the supply chain
.
Critics later warned it set an "unfortunate precedent" for future cyber incidents . Commentators noted that the government was conveying a precarious message regarding cyber threats by stepping in to support a private company hit by a cyberattack
.
No confirmed reporting about a Jordanian hacker simultaneously breaching JLR's networks was found in the available source evidence. None of the cited articles reference this detail, and it appears to be unsubstantiated in the available evidence. If a reader has a source for this claim, independent verification is recommended.
The JLR attack underscores several critical lessons:
As of the most detailed open-source reporting, the specific Russian state-linked hacking group has not been formally identified at the operational unit level, and no government minister has named a culprit . The attribution remains a work in progress, but the direction of the investigation is clear: what began as a phone call ended as the most expensive cyberattack in British history.
Studio Global AI
Use this topic as a starting point for a fresh source-backed answer, then compare citations before you share it.
Russian hackers executed the 2025 cyberattack on Jaguar Land Rover, causing an estimated £1.9 billion ($2.5 billion) in economic damage—the most expensive cyberattack in UK history.
Russian hackers executed the 2025 cyberattack on Jaguar Land Rover, causing an estimated £1.9 billion ($2.5 billion) in economic damage—the most expensive cyberattack in UK history. The breach began August 31, 2025 through a vishing campaign targeting JLR's IT helpdesk.
Loading comments...
Comments
0 comments