Skip to content
JAENES
CLeak confirmedSeptember 29, 2026 announced

TOPPAN(損保ジャパン)Data breach / unauthorized access incident

笹尾 祐太朗の写真Reviewed by Yutaro SasaoWritten by Leak Watch editorial team published ・ updated
Occurred on
September 1, 2026
Announced on
September 29, 2026
Severity
CLimited data such as email addresses and identifiers.
Scale
177,426 people
Main impact
Kana names and policy numbers, etc. for 177,426 individuals (possible duplicates) were mistakenly sent to one other non-life insurer, but complete deletion by the recipient has been confirmed. Email addresses, postal addresses, bank account information, etc. were not included.
Information involved
Email addressCard & payment dataHome addressFull name
Cause / key point
Erroneous manual operation by contractor TOPPAN and inadequate verification procedures.About Supply chain attacks (via vendors & shared services)
Industry
Finance & insurance
Listing / capital
Listed company東証プライム 7911(TOPPANホールディングス)
Last updated
October 20, 2026

Stock price reaction to the disclosureTOPPANホールディングス / 東証プライム 7911

2026.09.09 〜 2026.10.20Loading…

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.

Email addressCard & payment dataHome addressFull nameHow severity is assessed →

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).

Incidents related to "メール"

Incidents where the damage spread through the same service or system.

Same attack method

Same industry

Attack method classification: Supply chain attacks (via vendors & shared services)(Compromising the provider instead of the user)

Read the Supply chain attacks (via vendors & shared services) guide and national trends →

← Back to Breach Watch