---
title: "Toyota (via supplier Kojima Industries) security incident"
description: "What the retained public evidence establishes about the Toyota (via supplier Kojima Industries) incident, its attack path, impact, and response."
incident_type: "Cybersecurity incident"
status: "active"
last_modified: "2026-09-19"
canonical_url: "https://www.ally.security/incidents/toyota-via-supplier-kojima-industries-security-incident-2022"
markdown_url: "https://www.ally.security/incidents/toyota-via-supplier-kojima-industries-security-incident-2022.md"
stix_url: "https://www.ally.security/incidents/toyota-via-supplier-kojima-industries-security-incident-2022/stix.json"
---

# Toyota (via supplier Kojima Industries) security incident

The retained public source describes the Toyota (via supplier Kojima Industries) incident as Supplier ransomware/system fault. Other material details remain unresolved.

Last modified Sep 19, 2026 · 1 source

## Summary

- **Environment:** Automotive/Manufacturing
- **Operational impact:** The reviewed source does not establish a precise operational or data impact
- **Financial impact:** No financial figure is established by the reviewed source evidence

## What happened

In 2022, Toyota Motor Corporation experienced an incident in its automotive/manufacturing environment. The retained source describes the attack path as follows: Supplier ransomware/system fault. [1](#source-1)

## Impact

- The reviewed source does not establish a precise affected-person count, data scope, or operational consequence.
- No financial loss, ransom amount, recovery cost, or regulatory penalty is established by the reviewed source evidence.

## Threat Group & Attack Vector

The retained source describes the attack path as follows: Supplier ransomware/system fault. The canonical record does not add intrusion steps beyond those supported by the source. [1](#source-1)

### Actors

- No threat actor group has been identified in the reviewed public evidence.

### TTPs

- [T1486 — Data Encrypted for Impact](https://attack.mitre.org/techniques/T1486/) — mapped from the cited behavior. [1](#source-1)

## Response

The reviewed source does not describe containment, notification, or restoration steps in enough detail to summarize them responsibly.

This account is bounded to [Deepening Ties in Difficult Times—1 Year on from Kojima Industries Cyberattack](https://toyotatimes.jp/en/newscast/008.html). Details absent from that evidence are left unresolved rather than inferred. [1](#source-1)

## Assets

[Download the case-scoped STIX 2.1 bundle](<https://www.ally.security/incidents/toyota-via-supplier-kojima-industries-security-incident-2022/stix.json>)

## Sources

Primary source records used to research this incident.

<a id="source-1"></a>

### Deepening Ties in Difficult Times—1 Year on from Kojima Industries Cyberattack

official · Toyota Times

<https://toyotatimes.jp/en/newscast/008.html>

<details>
<summary>Evidence ledger</summary>

Review the supporting structured claims.

1. **Resulted In · 100% confidence · current**  
   Toyota (via supplier Kojima Industries) security incident: The reviewed source documents the toyota (via supplier kojima industries) security incident involving Toyota Motor Corporation, Kojima Industries Corporation.
2. **Used Attack Technique · 90% confidence · current**  
   Toyota (via supplier Kojima Industries) security incident: https://attack.mitre.org/techniques/T1486/
3. **Affected Organization · 100% confidence · current**  
   Toyota (via supplier Kojima Industries) security incident: Kojima Industries Corporation
4. **Affected Organization · 100% confidence · current**  
   Toyota (via supplier Kojima Industries) security incident: Toyota Motor Corporation
5. **Resulted In · 88% confidence · current**  
   Toyota (via supplier Kojima Industries) security incident: Supplier ransomware/system fault.

</details>