Skip to content
JAENES
BPossible leakOctober 30, 2026 announced

三菱自動車Data breach / unauthorized access incident

笹尾 祐太朗の写真Reviewed by Yutaro SasaoWritten by Leak Watch editorial team published ・ updated
Occurred on
October 9, 2026
Announced on
October 30, 2026
Severity
BIncidents centered on names and contact details.
Scale
24,480 records
Main impact
Customer information for two dealerships may have been viewed by third parties, and at least 2万4480件分 of names, transaction histories, and purchased vehicle information may have been leaked. No payment information leakage has been confirmed.
Information involved
Full name
Cause / key point
Unauthorized access caused by a third-party illicit login to Microsoft 365 used by dealership employees, which allowed customer information within the accounts to be viewed.About Abuse of credentials
Industry
Manufacturing
Listing / capital
Listed company7211
Last updated
October 31, 2026

Stock price reaction to the disclosure三菱自動車 7211

2026.10.10 〜 2026.10.31Loading…

Stock information is reference data based on Yahoo Finance and may be delayed. This site does not solicit or advise investment and does not guarantee the accuracy or completeness of this information. We accept no liability for any investment decision based on it.

Where to go for this information

The steps themselves are on the protection guide. These links match the kinds of data in this incident, plus support contacts.

Ask AI about this incident

Opens an AI chat with this page's URL already in the prompt. Treat the answer as a starting point — always verify with the official sources listed above.

Ask ChatGPT ↗Search Perplexity ↗

Is this incident worth paying attention to?

Written & reviewed

笹尾 祐太朗の写真

Reviewed byYutaro SasaoFounder & CEO, MediaLeap Inc.

CEO of MediaLeap Inc. Working on both sides of web advertising and web media since 2013; founded the company in May 2025.

Review scope: cross-checking against primary sources (official and government announcements), verifying claims stay within the facts, and checking source attribution。Last reviewed:

Written by:Leak Watch editorial team (AI-assisted drafts verified against sources by the editorial team) · Reviewer profile · Request a correction

Related incidents

Browse the database →

Incidents sharing the same company, service, attack method or industry (grouped automatically from the disclosures).

← Back to Breach Watch