Investigation Report on Jaguar Land Rover Cyberattack

Investigation Report on Jaguar Land Rover Cyberattack

Jaguar Land Rover experienced a major cyber incident on September 2, 2025, that disrupted global IT systems and halted manufacturing and retail operations, with leaked internal data and screenshots posted by a Telegram channel claiming ties to Scattered Spider, Lapsus$, and ShinyHunters. Earlier HELLCAT activity using Infostealer-harvested Jira credentials and subsequent data dumps increased risk of credential theft, IP exposure, and targeted follow-on attacks. #HELLCAT #ShinyHunters

Keypoints

  • JLR’s global IT systems were shut down on September 2, 2025, causing production and retail halts and extended suspension of manufacturing through at least September 24, 2025.
  • Screenshots and internal data were posted on a Telegram channel calling itself Scattered Lapsus$ Hunters, revealing internal domains (e.g., jlrint.com), debug logs, and backend code snippets tied to infotainment and authentication systems.
  • Earlier breaches attributed to HELLCAT used Infostealer malware to harvest Jira credentials, resulting in large data dumps (≈700 documents and an additional ~350 GB) containing source code, development logs, and employee data.
  • Exposed artifacts include Pivi Pro infotainment debug logs, EV charging logic details, and backend user-to-vehicle profile code that could enable reverse engineering or targeted exploitation of connected services.
  • Actors have threatened further disruptive actions and targeted UK telecoms and officials; multiple impersonating Telegram accounts are amplifying old breach content to create confusion.
  • CYFIRMA assesses medium confidence that ShinyHunters Collective is likely involved but awaits definitive forensic attribution; the incident highlights IT/OT risks in the automotive sector.
  • Recommendations include enforcing MFA and credential rotation, strengthening detection (endpoint and network), conducting supplier audits, and running red-team/tabletop exercises covering IT and OT scenarios.

MITRE Techniques

  • [T1566 ] Phishing – Spear-phishing used to obtain credentials for internal systems (article: “spear-phishing … for initial access”).
  • [T1078 ] Valid Accounts – Use of stolen Jira/employee credentials to access JLR systems (“stolen Jira credentials harvested via Infostealer malware”).
  • [T1059.001 ] Command and Scripting Interpreter: PowerShell – PowerShell used for persistence or deploying malware (“PowerShell-based persistence, AMSI bypasses, and reflective code loading”).
  • [T1547.001 ] Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder – Scripts modifying registry for persistence (noted as potential persistence method: “if scripts modified registry for persistence”).
  • [T1068 ] Exploitation for Privilege Escalation – Leveraging misconfigured host entries for privilege escalation (“leveraging misconfigured host entries”).
  • [T1027 ] Obfuscated Files or Information – Use of obfuscation to evade detection (screenshots/code indicate obfuscation of activity: “screenshots/code indicate obfuscation of activity”).
  • [T1555.003 ] Credentials from Password Stores: Credentials from Web Browsers – Theft of Jira credentials from browser-stored or harvested stores (“Jira credentials harvested via Infostealer malware”).
  • [T1083 ] File and Directory Discovery – Discovery of system paths and debug logs shown in leaked screenshots (“screenshots show system paths, debug logs”).
  • [T1046 ] Network Service Discovery – Enumeration of internal DNS and host resolution entries (“internal DNS and host resolution entries”).
  • [T1005 ] Data from Local System – Collection of debug logs, source code, and backend files (“debug logs, source code, backend files”).
  • [T1114 ] Email Collection – Harvesting internal communications as potential data sources (“if internal communication/data harvested”).
  • [T1041 ] Exfiltration over C2 Channel – Exfiltration of sensitive code and logs possibly via C2 (“sensitive code, Jira issues, debug logs”).
  • [T1071.001 ] Application Layer Protocol – Use of HTTPS/HTTP for C2 communications (“C2 over HTTPS/HTTP for persistence”).
  • [T1499 ] Endpoint Denial of Service – Threats and actions to disrupt operational systems (“threat of disruption to operational systems”).
  • [T1489 ] Service Stop – Stopping services and shutting down IT/retail systems as part of the attack (“shutdown of IT/retail systems as part of attack strategy”).

Indicators of Compromise

  • [Domain ] internal domain tied to JLR systems – jlrint.com (revealed in shared screenshots).
  • [File/Artifact ] debug logs and backend code snippets – PIVI infotainment debug log (SIMS-23441), backend user-to-vehicle profile code (exposed JSON handling and auth logic).
  • [Data Dump ] leaked documents and datasets – ~700 internal documents and an additional ~350 GB of data including source code and employee data (posted by HELLCAT/actors).
  • [Credentials ] compromised account credentials – stolen Jira credentials harvested via Infostealer (used for initial access).
  • [Channel ] threat actor communications – Telegram channel “Scattered Lapsus$ Hunters” posting screenshots, and dark forum posts by actors “Rey” and “APTS”.


Read more: https://www.cyfirma.com/research/investigation-report-on-jaguar-land-rover-cyberattack/