Japan’s October 2026 breaches: a briefing

Matt Ketchum, MKUltraman · Data as of 16 November 2026 · Scope: incidents disclosed 1–31 October 2026 · Source: the Japan Cybersecurity Tracker

The 30-second briefing

Key facts. Organisations in Japan published 692 breach notices in October 2026, seven times September’s 99. Those notices trace back to about 281 distinct breaches. 458 of the 692 notices (66.2%) came from organisations hit through a supplier, and five supplier breaches alone produced 296 notices (42.8%). Where a notice gave a figure, the headline numbers add up to about 344 million records, in mixed units.

Who should act. Anyone whose customer, member or resident data sits with an outside service: bulk-email senders, website and form builders, community and booking platforms. Local governments most of all: 174 of their 187 notices (93.0%) came through a supplier.

One first action. List every supplier that holds your personal data, put one named person in charge of each, and ask each in writing whether it was affected and what of yours it still holds.

Biggest uncertainty. How attackers got in. 166 of the 281 distinct breaches (59.1%) do not say. The tail is also still arriving: one supplier that disclosed on 28 October had produced 265 further customer notices by 16 November.

Posture

October was not one catastrophe. It was a few dozen supplier breaches, each copied into tens of customer notices, on top of a steady run of organisations breached in their own systems. Nobody needs to panic. Most organisations do need to know which of their suppliers hold personal data, and who inside the organisation answers for each one. Japan’s heavy use of outside contractors is well known; what is new is that the notices now let us count what that costs.

What’s affected

633 of the 692 notices (91.5%) list at least one type of data. The shares below use those 633 as the base. Service disruption uses all 692.

Data type Notices Share
Email addresses 446 446 of 633 (70.5%)
Names 385 385 of 633 (60.8%)
Phone numbers 218 218 of 633 (34.4%)
Postal addresses 165 165 of 633 (26.1%)
Date of birth 100 100 of 633 (15.8%)
Passwords (51 of these say hashed or encrypted) 90 90 of 633 (14.2%)
Payment card data (including partial numbers) 21 21 of 633 (3.3%)
Service suspended, stopped or taken offline 220 220 of 692 (31.8%)

Data types are matched on the wording of each notice. A notice that says “no card data” is not counted as card data. Four more notices say card data may be involved and are not counted.

The pattern is contact data, in bulk. That is exactly what a phishing campaign needs, which is why so many notices end with a warning to watch for suspicious mail.

October in numbers

Weekly counts by disclosure date. October 1 was a Thursday, so the first week is short.

Week Notices Through a supplier Own systems Supplier’s own notice Unclear
1–4 Oct 13 0 of 13 (0.0%) 13 0 0
5–11 Oct 96 58 of 96 (60.4%) 34 4 0
12–18 Oct 152 110 of 152 (72.4%) 31 11 0
19–25 Oct 239 174 of 239 (72.8%) 42 21 2
26–31 Oct 192 116 of 192 (60.4%) 62 13 1
October 692 458 of 692 (66.2%) 182 49 3

“Own systems” means the organisation’s own systems were breached. “Supplier’s own notice” is a supplier announcing its own breach.

The supplier waves arrive a few days after each supplier’s own announcement, as customers check their lists and publish. The last week is notable for the other column: own-system notices rose to 62, the highest of the month.

Notices vs distinct breaches

This is the key split. When one supplier is breached, every customer that publishes counts as a notice, but it is still one breach. To count breaches, I collapsed every notice linked to a named supplier into that supplier’s breach, and counted each own-system incident once.

About 281 distinct breaches produced the 692 October notices. 69 named supplier breaches account for 480 notices. 182 were breaches of the organisation’s own systems, 2 are unclear, and 28 came through a supplier the notice does not name. Those 28 are counted one each, so 281 is an upper bound; if some share a supplier, the true number is lower.

Most supplier breaches are small: 35 of the 69 (50.7%) produced a single notice. A handful are not.

Supplier breach What it does October notices Share of 692
Blastmail (Rakus Lite Cloud) Bulk email delivery 99 99 of 692 (14.3%)
Arcadia Bulk notification service for local governments and schools 69 69 of 692 (10.0%)
Studio No-code website builder, including forms 64 64 of 692 (9.2%)
Commune Corporate customer-community platform 38 38 of 692 (5.5%)
Furusato Choice (Trust Bank) Hometown-tax donation portal 26 26 of 692 (3.8%)
Top five 296 296 of 692 (42.8%)
Next: Cuenote FC (Yumi Link) Bulk email delivery 24 24 of 692 (3.5%)

Five of 281 distinct breaches (1.8%) made up 42.8% of the month’s notices. Three of the top six are bulk-messaging services (Blastmail, Arcadia and Cuenote FC), and together they produced 192 of 692 notices (27.7%).

Arara Message is the obvious absentee. Arara disclosed its own breach on 28 October, so only 9 of its notices fall in October. Another 265 followed between 1 and 16 November. The Arara Message page tracks them by name.

The second ring

Some organisations never contracted with the breached supplier. Their own supplier did. The data shows this in October, though the chains are short and the counts small:

  • Saitama Prefecture’s smart-farming site was affected through a contractor that used Cuenote FC.

  • Okinawa Prefecture’s mail magazines and park bookings were reached through a tourism bureau and a booking service that used Blastmail.

  • Three securities firms and a rail group were affected by a breach at Securitize Japan, a supplier to their contractor NTT Data.

  • Two universities were reached through an unnamed subcontractor of their system operator, NEC.

November makes the point more loudly. Of the 265 Arara notices disclosed in November, 100 (37.7%) came through another supplier, including 60 local governments using TKC systems and 13 online-shop operators using MakeShop.

Sectors two ways

Counting notices and counting breaches give different pictures. The second column counts breaches of the organisation’s own systems, including suppliers that announced breaches of their own systems (231 in October).

Sector Notices Own-system breaches
Government / public sector 187 of 692 (27.0%) 13 of 231 (5.6%)
IT / internet / software services 89 of 692 (12.9%) 54 of 231 (23.4%)
Retail / e-commerce 77 of 692 (11.1%) 43 of 231 (18.6%)
Media / entertainment 59 of 692 (8.5%) 24 of 231 (10.4%)
Other 56 of 692 (8.1%) 10 of 231 (4.3%)
Finance / insurance 44 of 692 (6.4%) 18 of 231 (7.8%)
Corporate community sites 36 of 692 (5.2%) 0 of 231 (0.0%)
Education / research 36 of 692 (5.2%) 18 of 231 (7.8%)
Manufacturing / construction / utilities 28 of 692 (4.0%) 13 of 231 (5.6%)
Transport / logistics 23 of 692 (3.3%) 5 of 231 (2.2%)
Travel / hospitality / leisure 22 of 692 (3.2%) 15 of 231 (6.5%)
Healthcare / pharma 20 of 692 (2.9%) 12 of 231 (5.2%)
Restaurant / food service 15 of 692 (2.2%) 6 of 231 (2.6%)

Government tops the notice count and sits near the bottom for its own systems. That does not make the public sector safe. It means its exposure is mostly held by suppliers. Software and online-service companies, which are often those suppliers, top the own-system list.

How attackers got in

The route is stated for only 115 of the 281 distinct breaches (40.9%). 166 (59.1%) say “unauthorized access” and nothing more, including Blastmail, Arcadia and Commune. The shares below use only the 115 that state a route, so treat them as a sketch.

Route, in plain English Distinct breaches Closest MITRE ATT&CK technique
Misused account: stolen or guessed passwords, hijacked email or admin accounts, reused passwords tried in bulk 52 of 115 (45.2%) Valid Accounts (T1078)
Flaw in an internet-facing system: an unpatched or vulnerable website, plugin or server 28 of 115 (24.3%) Exploit Public-Facing Application (T1190)
App or API abuse: using an app’s own functions or programming interface (API) in ways it should not allow 16 of 115 (13.9%) Usually also T1190
Ransomware: files encrypted, often with data taken first 12 of 115 (10.4%) Data Encrypted for Impact (T1486), which describes the damage, not the way in
Other: malware on a contractor’s computer, payment fraud, outages 7 of 115 (6.1%) Varies

MITRE ATT&CK is a public catalogue of attacker techniques that security teams use as a shared vocabulary. Supplier breaches take the route stated in the supplier’s own notice. Cuenote FC is counted as a misused account, though its notice says a software flaw was used first to obtain staff credentials.

One flaw can travel far: Studio’s website-builder flaw alone produced 64 notices. But by distinct breaches, misused accounts lead: an email account that sends phishing, an admin login reused from somewhere else, a supplier’s staff credentials. That is the cheaper problem to fix.

Records

October’s deduplicated total is 343,795,492. Notices whose figures already sit inside a supplier’s own total are left out: 344 of 692 (49.7%). That way each supplier breach counts once. Of the 348 that remain, 194 (55.7%) give a number.

The unit is the catch. Notices count email addresses, people, accounts or simply “records”, and the same person can appear in many of them. Read this as the sum of headline figures, not as a count of people.

Unit stated Records Share of total
Records, unit unspecified 216,119,496 62.9%
Mixed units 83,106,481 24.2%
Unit not disclosed 22,514,733 6.5%
People 12,689,326 3.7%
Email addresses 7,234,372 2.1%
Card details 1,786,751 0.5%
Accounts and form submissions 344,333 0.1%

A few breaches carry the total. The top five make up 56.3% and the top ten 70.9%. The median notice with a figure is 14,517.

Organisation Headline figure Breached
Arara (Arara Message) 81,329,467 email addresses Supplier’s own systems
Yumi Link (Cuenote FC) 47,864,147 records (gross, 49 systems) Supplier’s own systems
Ryohin Keikaku (MUJI app) 27,260,000 records Own systems
SourceNext 22,519,960 records Own systems
Skyticket (Adventure) 14,640,000 records Own systems
Capcom (CAPCOM ID) 11,774,247 records Own systems
Burger King Japan 11,180,000 records Own systems
Yakiniku King (Monogatari Corporation) 10,788,963 records Own systems

Sagawa Express’s figure of up to 53.23 million is not in October’s total, because its first notice came on 30 September.

Disclosure speed

Only notices with an exact discovery date and an exact disclosure date are used: 294 of 692 (42.5%). Discovery here means when the organisation says it found out, which for a supplier’s customer is often when the supplier told it.

Group Notices with both dates Median days, discovery to disclosure Disclosed within 7 days
All 294 2 251 of 294 (85.4%)
Own systems 109 3 79 of 109 (72.5%)
Through a supplier 143 2 137 of 143 (95.8%)
Supplier’s own notice 39 3 32 of 39 (82.1%)

54 of 294 (18.4%) disclosed on the day they found out. 10 of 294 (3.4%) took more than 30 days, the slowest 417 days for an online shop where card-skimming code sat on the payment page. Telling people quickly is mostly working. Finding out quickly is the harder part: one essay-scoring service says a planted web shell, a hidden back door on its server, had been there for about ten months.

Outside counts that corroborate

Other counts use different rules and scopes, and none of them should be added to the tracker’s. They point the same way.

  • The Personal Information Protection Commission (PPC) material of 28 October 2026 shows 830 initial reports of personal-data leaks from unauthorized access between 1 and 16 October, against 303 for all of September. The PPC notes that a client and its contractor may both report the same event, and that reports from financial and telecom firms and from public bodies are not included.

  • Tokyo Shoko Research (TSR) counted 109 leak incidents at listed companies and their subsidiaries in October (a preliminary figure), out of 215 for January to October. Until September the monthly count was in the teens. TSR’s scope excludes unlisted companies and government.

  • The Cabinet Secretariat’s emergency cybersecurity package of 6 November 2026 includes a chart of incident reports from critical-infrastructure operators to the National Cybersecurity Office (NCO) showing a sharp rise in October from a low monthly level (materials, page 6). The chart prints no values, so I do not quote a number. The package text names inadequate basic measures at the organisation or its contractors as a common thread.

Patterns

  1. One breach, many notices. About 281 breaches produced 692 notices, and five of them produced 296 (42.8%).

  2. Bulk messaging is the soft spot. Three bulk-mail and notification services produced 192 of 692 notices (27.7%). Stolen mailing lists turn into phishing within days.

  3. The public sector’s exposure is borrowed. 174 of 187 government notices (93.0%) came through a supplier, and 13 government breaches were of its own systems.

  4. Where the route is known, accounts lead. Misused accounts explain 52 of 115 breaches with a stated route (45.2%).

  5. Notices are quick; detection is slow. The median gap from discovery to disclosure is 2 days, but some intruders sat in systems for months first.

  6. Chains are getting longer. In November, 100 of 265 Arara notices (37.7%) came through another supplier.

Decisions for leadership

The decision is simple to state and tedious to do. Review every supplier that touches personal data. Keep the ones that are necessary. Bring the rest in-house or drop them. This is not about blaming suppliers, who are often better at security than their customers. It is about having fewer places your data can leak from, each with a clear owner, while keeping the services that earn their place.

The case is not only security. Fewer suppliers and clear ownership mean fewer contracts, fewer logins, fewer invoices and fewer surprise notices to write. It is operational efficiency: less work, lower cost and fewer fires. Being able to say “we know exactly who holds your data, and why” is also a trust signal customers and residents now notice.

When Action Owner Done when
30 days Inventory every supplier holding personal data, including mail, forms, websites, booking and analytics tools. Head of IT or security, with procurement A single list exists, each line with data types, record count and a named internal owner.
30 days Ask each supplier in writing whether it was affected in October or November and what of yours it holds. Named supplier owners Every supplier has replied, or is escalated.
30 days Turn on phishing-resistant multi-factor authentication (MFA), such as passkeys or hardware security keys, for admin and supplier-portal accounts. IT operations Admin accounts covered first; supplier portals by day 90; exceptions listed with an end date.
60 days Decide keep, consolidate, bring in-house or drop for each supplier. Delete data you no longer need, at the supplier and at home. Business owners, with legal Each supplier has a decision and a date; deletion confirmed in writing.
60 days Move every sending domain toward DMARC “reject”, the email-authentication setting that tells receivers to refuse mail faking your domain. IT operations or email administrator Policy at reject for all sending and parked domains.
90 days Add notice clauses to supplier contracts: how fast they must tell you, what they must tell you, and who pays for notification. Legal and procurement Clauses in all critical contracts; others at renewal.
90 days Rehearse a supplier breach: draft customer notice, phishing warning and helpdesk script. Communications and security One exercise run; templates approved.

DMARC will not stop phishing sent through a hijacked account at your own mail supplier, because that mail is genuinely yours. It does stop attackers from borrowing your domain elsewhere, and it is cheap.

Measure Why Suggested target
Share of personal-data suppliers with a named internal owner Ownership is what makes the rest happen. 100% within 60 days
Number of suppliers holding personal data Fewer places for data to leak, and less to manage. Down quarter on quarter
Personal-data records held at suppliers Data you no longer hold cannot leak. Falling every quarter
Sending domains enforcing DMARC reject Stops spoofing of your domain. All sending and parked domains within 90 days
Admin and supplier access with phishing-resistant MFA Misused accounts lead the stated routes. 100% of admin accounts within 90 days
Personal-data supplier contracts with a notice clause You hear first, not from the news. All critical contracts within 90 days; the rest at renewal
Days from a supplier’s notice to your own Customers deserve prompt warning. Median within 3 days

Targets are suggestions to start a conversation, not regulatory requirements.

What remains unknown

  • How most attackers got in. 166 of 281 breaches (59.1%) do not say.

  • Whether the October wave was one campaign or many. Some notices describe similar methods, but the data does not tie them to a single attacker.

  • How many people were really affected. The record units are mixed and overlap, and 154 of the 348 counted notices (44.3%) give no number.

  • Who has not published. Organisations that stayed silent are not counted, so every figure here is a floor.

  • How much of the Arara chain, and other long chains, is still to come.

  • Whether “no leak confirmed” holds. Many notices are first reports, and later reports often revise upwards.

How we counted

Each row of the tracker is one organisation’s published notice about a cyber incident in Japan. This briefing uses rows whose disclosure date falls between 1 and 31 October 2026, from the snapshot of 16 November 2026. Notices about October that were found late were added up to that date.

  • Included: incidents disclosed by the organisation itself, or a supplier’s notice confirmed by the customer’s own notice. Hijacked email and admin accounts count even when no leak is confirmed.

  • Not included: ransomware gangs’ claims on the dark web without a notice, lost USB sticks and other physical losses, and precautionary shutdowns with no incident.

  • “No leak confirmed” is recorded as stated. It is not read as “no leak”.

  • Sources: 563 of 692 notices (81.4%) link to the organisation’s own notice, filing or press release. 129 (18.6%) currently cite press or aggregator coverage only.

  • Supplier links: of the 458 notices through a supplier, 422 (92.1%) name the supplier, 9 (2.0%) are inferred from the service described, and 27 (5.9%) do not name one.

  • Distinct breaches: notices are collapsed to the parent breached supplier named in the data. Own-system incidents and unnamed-supplier notices count one each.

  • Records: the headline or maximum figure each notice gives. Blank stays blank, not zero. Figures already inside a supplier’s total are excluded from the sum.

  • Limits: categories come from the wording of notices, much of it translated from Japanese. The data is a snapshot and changes as reports are revised.

The full row-level dataset is available on request through the dataset page, which also explains the method and how to cite it.

If you need any help, don’t hesitate to get in touch.

Matt Ketchum