IOTW: Car production halted by Toyota after suspected cyber-attack

Supplier to Japanese car manufacturer experienced a system failure as a result of a presumed malware attack

Add bookmark

One of Toyota Japan’s suppliers was hit by a cyber-attack which led to the suspension of production from 28 February and resuming on 2 March.

First reported by the Nikkei Asia news agency, the cyber-attack affected Kojima Industries which manufactures both interior and exterior car parts and is a part of Toyota’s just-in-time supply chain in Japan.

The issue resulted in 14 plants and 28 production lines being suspended. Plants outside of Japan have not been affected.

In a statement on 1 March 2022, Toyota said: “We would like to apologize again to our customers, suppliers, and other related parties for any inconvenience caused by today's sudden shutdown.”

The car manufacturer has not provided any public statement on the nature of the “system failure”. Nikkei Asia reported that Kojima Industries said it was investigating the origin of the attack and the specific malware involved.

Become a Cyber Security Hub member and gain exclusive access to our upcoming digital events, industry reports and expert webinars

Malware in Japan

While the type of malware used in the attack has not been confirmed, just days before the Toyota incident the Japan Computer Emergency Response Team Coordination Center (JPCERT/CC) released an alert regarding the re-emergence of Emotet Malware infection activities.

The alert, last updated on 25 February, said the number of reports regarding the Emotet Malware had increased “in particular since the first week of February 2022”.

“Emotet has been observed since late November 2021 and is mainly distributed through emails as an Excel or Word file with macros (or as a password protected Zip folder containing such a file). Enabling the macro after opening the file leads to the infection of Emotet,” the JPCERT/CC alert explains.

External party risk

Car manufactures are one of many groups heavily reliant on third-party vendors, which makes it critical that organizations have a good grip on how to manage the security and risk of each external party.

Ahead of CS Hub’s Third Party Risk Management Digital Summit, Robin Smith, head of cyber and information security at Aston Martin Lagonda in the UK, spoke to CS Hub about implementing a cyber threat intelligence management (CTIM) model that can be used to understand risk intelligence within an organization’s supply chain.

He highlighted that forecasting and evidence-based responses are key to any organization’s ability to plan third-party risk and direct resources to the correct areas.

To find out more register here for the Third Party Risk Management 2022 Digital Summit, taking place online on 08-09 March.


More From Incident of the Week

IOTW: Victoria Court recordings exposed in suspected ransomware attack

Unauthorized access disrupted audio visual in-court technology network impacting video recordings, a...

 2024-01-05  by Michael Hill
IOTW: Victoria Court recordings exposed in suspected ransomware attack

IOTW: Xfinity data breach impacts 35 million customers

Exposed data includes usernames, hashed passwords and social security numbers

 2023-12-22  by Michael Hill
IOTW: Xfinity data breach impacts 35 million customers

IOTW: Russia-linked cyber attack targets Ukraine’s biggest phone operator

Powerful attack knocked out internet access and mobile communications, damaging IT infrastructure

 2023-12-15  by Michael Hill
IOTW: Russia-linked cyber attack targets Ukraine’s biggest phone operator

IOTW: HTC confirms cyber attack as BlackCat ransomware gang teases stolen data

BlackCat/ALPHV ransomware group leaked photos of what appears to be stolen passports, contact lists,...

 2023-12-08  by Michael Hill
IOTW: HTC confirms cyber attack as BlackCat ransomware gang teases stolen data

IOTW: Okta data breach affects all customer support users

Hackers stole information on all users of Okta’s customer support system

 2023-12-01  by Michael Hill
IOTW: Okta data breach affects all customer support users

Recommended