Cybersecurity 4 min read

Osaka Says 1.08 Million Email Addresses Leaked as Arara Breach Count Reaches 81 Million

The city traces its leak to a mail service used by contractor TKC. We lined up six notices from Arara, TKC, SEGA and Osaka to show how the vendor's own count grew 27-fold in eight days.

Kenji Tanaka
Developer Tools & Cloud Analyst
Published 15 Nov 2026, 2:22 PM (SGT)
Share:
A person typing on a laptop with an email inbox open on the screen A person typing on a laptop with an email inbox open on the screen Photo by cottonbro studio on Pexels
Advertisement

15 NOV 2026 — The City of Osaka said on 13 November that 1,078,713 email addresses belonging to users of its online administrative system had leaked. The city's notice blames unauthorised access to a mail-delivery service used by its system contractor, TKC Corporation. Anyone who received mail from the system between 1 July and 31 October 2026 is affected.

The city does not name the delivery service. TKC does. Its 4 November update says it outsources email delivery to Arara Inc. and its "Arara Message" platform. Arara, a subsidiary of PayCloud Holdings, stopped the whole service on 31 October and has revised its count of stolen addresses twice since. The table below sets the organisations' own notices side by side. Figures are as each notice states them, and the translations are ours.

NoticeDateEmail addresses statedOther detail in the notice
Arara, first notice29 OctAbout 3.01 millionOne shared environment; cause given as a web-server vulnerability (as restated in the second notice)
Arara, second notice2 NovAbout 77 million, under reviewClient environments on 97 servers; names and other member data taken, varying by client; up to about 7.13 million suspicious emails sent through the service
TKC, third update4 NovUp to 2,230,812Addresses only; no message bodies, My Number data or municipal application details
PayCloud Holdings, third notice6 Nov81,329,467 after removing duplicatesUp to about 380 client companies, under review; 47,044,380 of the addresses came with attribute data
SEGA9 Nov2,196,04492,273 with delivery-related data; names, dates of birth and card details not leaked; no misuse confirmed as of 9 Nov
City of Osaka13 Nov1,078,713Users who received mail from the system, 1 Jul to 31 Oct; count is high because of a bulk notice to all registered users on 16 Sep

A count that grew 27-fold

Arara's figure went from about 3.01 million to 81,329,467 in eight days, roughly 27 times the first estimate (81,329,467 divided by 3.01 million is 27.0). The first number is itself rounded, so the multiple is approximate. The third notice explains the jump. The attacker reached 97 client servers between 28 and 31 October, and a separate cloud environment holding another 3,249,492 addresses turned up later.

Advertisement

We checked that notice's table against itself. Its three components (78,102,937, 2,842,400 and 3,249,492) add up to 84,194,829. Taking out the two duplicate counts it lists, 2,818,091 and 47,271, leaves exactly 81,329,467. The same table splits the total into 34,285,087 bare addresses and 47,044,380 with attribute data, so about 58% of the stolen addresses came with something more. Arara's 6 November statement says that, depending on the client, this could include names, sex, dates of birth, phone numbers, membership numbers and addresses. The company says the split is still being checked, and that the figures count addresses, not people.

Osaka's share, and what it cannot show

Osaka's 1,078,713 is about 1.3% of Arara's de-duplicated total. Against TKC's ceiling of 2,230,812 for all users of its systems, the city's count is about 48%. SEGA and Osaka together come to 3,274,757, already more than Arara's whole first estimate. None of these notices says how far client lists overlap, so adding them up does not give a national figure.

Arara says it reported the incident to police on 29 October and has filed reports with the Personal Information Protection Commission, most recently on 6 November. No restart date has been set. The city says it will not answer individual questions about whether a given address was leaked. It asks users to check their own inboxes for mail from the system in the affected period, and to ignore links and attachments in unexpected messages claiming to come from the city.

Advertisement
Kenji Tanaka
Developer Tools & Cloud Analyst

Kenji Tanaka covers developer tools, cloud platforms, DevOps, CI/CD, and software supply-chain topics for RECATOOLS.

View author profile → · Editorial policy

About this byline Kenji Tanaka is a RECATOOLS editorial persona for developer tools, cloud, DevOps, and software supply-chain coverage. Articles are produced and reviewed under RECATOOLS editorial supervision.

Corrections policy

Advertisement