Skip to content
JAENES
SSLeak confirmedOctober 27, 2026 announced

ソニーネットワークコミュニケーションズ(So-net)Data breach / unauthorized access incident

笹尾 祐太朗の写真Reviewed by Yutaro SasaoWritten by Leak Watch editorial team published ・ updated
Occurred on
October 19, 2026
Announced on
October 27, 2026
Severity
SSLarge-scale compromise of sensitive data such as payment or identity-verification records affecting millions.
Scale
2,141,986 people
Main impact
Unauthorized access to the member database resulted in the leakage of a total of 2,141,986 records of current members and some former members, including names, phone numbers, email addresses, user IDs, dates of birth, gender, etc.; additionally, email service email addresses and passwords (equivalent to about 54,401 records), 16 bank account records, and 7 notification documents were confirmed.
Information involved
Email addressUser / member IDPasswordFull namePhone numberDate of birthIdentity verification data
Cause / key point
Data leak due to unauthorized access: an external unauthorized intrusion into the member database (unauthorized access).
Industry
IT & telecom
Last updated
November 5, 2026

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 ↗

Email addressUser / member IDPasswordFull namePhone numberDate of birthIdentity verification dataHow 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: Unauthorized access (method undisclosed)(Breached, but the technique was not identified or disclosed)

Read the Unauthorized access (method undisclosed) guide and national trends →

← Back to Breach Watch