16Threats

Japan's breach wave: what 53 million records teach

In the week of October 18–24, 2026, Japanese organizations disclosed a series of large data incidents. Parcel carrier Sagawa Express put its possible exposure at up to 53 million records, the largest count reported in Japan this year. The figures are not directly comparable, but the pattern is clear and relevant far beyond Japan.

01What was reported

Reported disclosures included Sagawa Express (up to 53.23 million records, including duplicates, possibly exposed), Capcom game accounts (about 11.77 million), the email delivery service Yumil Link (about 9 million cumulative), Times Car (6.63 million in a final report), the hometown-tax platform Furusato Choice (4.45 million) and others in e-commerce, retail and internet services.

Those numbers mix records with people and include duplicates, so they cannot simply be added together. Some are confirmed thefts; others are possible exposure still under investigation. Careful reading of the wording matters as much as the headline number.

02Suppliers are part of your attack surface

Three email delivery services were reported breached within a month, and a university's data leaked through a contractor. When a vendor sends your emails, stores your logs or processes your customers, an attack on that vendor can become your incident.

Keep a list of suppliers that hold personal data, know what they hold, and agree in writing how quickly they must tell you about a breach. Ask whether they enforce MFA for administrators and how they separate one customer's data from another's.

03Logs and old data are still data

One e-book service said most exposed records came from logs. Logs, exports and backups often contain names, emails and identifiers long after the business stopped needing them. Data that is not kept cannot be stolen.

Set retention periods, mask personal data in logs where possible, and delete test exports. Review which systems keep copies of customer data and who can access them.

04What to do this week

Map where customer data lives, including suppliers. Remove unnecessary copies. Check that administrative access to email platforms, cloud consoles and customer portals requires phishing-resistant MFA. Prepare a short customer notification template now, so you are not writing it during a crisis.

This article is based on reporting available on October 24, 2026; several investigations were still ongoing.

Sources & further reading

Japan Cyber Watch — Japan cybersecurity week in review, October 18–24, 2026

Security Boulevard — Top 10 breaches of the week

Continue with MindSec

Explore MindSec security awareness and defense training

All publicationsNext publicationAI ransomware: inside the exposed 'Phantom' setup
Skip to main content