---
title: "SBC Medical Group Data Breach Exposes Customer Emails"
date: "2026-11-20"
author: "Ahsan Luqman"
canonical_url: "https://aliasfleet.com/blog/sbc-medical-group-data-breach"
tags: ["Data Breach", "Email Privacy", "Healthcare"]
description: "SBC Medical Group disclosed on 19 November 2026 that unauthorised access extracted information for 1,624,000 customers, with email addresses among the fields."
---

# SBC Medical Group Data Breach Exposes Customer Emails

SBC Medical Group disclosed on 19 November 2026 that unauthorised access extracted information for 1,624,000 customers, with email addresses among the fields.

SBC Medical Group Holdings Inc. (Nasdaq: SBC) disclosed on 19 November 2026 that unauthorised access to databases operated by its Japanese subsidiary extracted customer information. The largest affected category covers 1,624,000 customers, with records from 2010 to 2023 that include names, email addresses and passwords among the fields. SBC detected the access on 16 November 2026 and reported the database incident to Japan's Personal Information Protection Commission the same day. A second, separate incident, also on 16 November, affected clinic administrator accounts on Tribeau, a third-party reservation service used by 56 clinics that SBC provides management services to.

## The disclosure and the regulatory report

The disclosure appeared as a [Business Wire release](https://www.financialcontent.com/article/bizwire-2026-11-19-sbc-medical-group-reports-cybersecurity-incidents-in-japan) on 19 November 2026 at 04:39 UTC, and Jiji Press carried it in full through its [English wire](https://jen.jiji.com/20261118771303/). SBC Medical Group provides management services to medical corporations and clinics in Japan, working across aesthetic healthcare, dermatology, orthopedics, fertility treatment, gynecology, dentistry, hair loss treatment and ophthalmology. The release treats the database incident and the Tribeau incident as two separate incidents, and states no common cause. It names no attacker and makes no mention of ransomware or extortion.

## Data extracted in the database incident

The release sets out five categories of customer information, giving a count and a record period for each. The largest category is basic personal information without reservation or treatment information, for 1,624,000 customers, covering records from 2010 to 2023. The fields in that category are names, sex, telephone numbers, email addresses, passwords, addresses, dates of birth, patient card numbers, member IDs and survey responses, with all or some of these items present depending on the record.

| Category | Individuals | Period |
| :--- | :--- | :--- |
| Basic personal information | 1,624,000 | 2010-2023 |
| Reservation requests through advertising, affiliate and campaign pages | 255,416 | 2007-2026 |
| Inquiries submitted through website forms | 217,769 | 2004-2026 |
| Treatment-monitor information | 4,513 | 2013-2026 |
| Reviews submitted directly to the group | 15,007 | 2015-2018 |

The reservation requests hold some or all of the basic information fields, together with the reservation-request information. The website inquiries hold some or all of the basic information fields, together with the content entered in the web inquiry forms. The treatment-monitor records hold some or all of the basic information fields, together with treatment descriptions and stored image file names, not the images themselves. The reviews hold some or all of the basic information fields, together with treatment names and review text.

Adding the five category counts gives 2,116,705. According to [Cybersecurity Market's analysis](https://cybersecuritymarket.com/sbc-medical-group-cyberattack-japan-customer-data-2026/) of the disclosure, the company has not established that the categories represent separate individuals, and the release gives no deduplicated total. One person who made a reservation request, submitted a website inquiry and left a review would appear in three categories, so adding the counts together would overstate what is known. Secondary reporting that states a single total for the incident is not supported by the release text. This article states the category counts and no combined total.

Employee information was also obtained. Account information for employees of the company's group and the medical institutions it supports was obtained, including names, IDs and passwords, involving approximately 20,000 records. For 459 employees, information provided at the time of employment was also affected, including bank account and pension-related information, withholding tax certificates and dependent exemption declarations.

Credit card information appeared in a small number of historical customer inquiries. According to the release, 14 individuals were affected in this way, and the company has confirmed that all of these credit cards were in a state in which additional payments could not be processed, such as having expired. The inquiry-form entries concerned run from 2010 to 2018.

## The Tribeau incident

The second incident stands apart from the database incident. On 16 November 2026, SBC was notified that clinic administrator accounts on Tribeau had been accessed without authorisation. Tribeau is a third-party reservation service used by 56 clinics to which the company provides management services. The platform operator grouped the accessed information in three sets. Reservation-only information covered 12,641 people: kana name, telephone number, age, requested treatment, special menu and optional notes. Three of those people had exchanged messages with a clinic, and their message contents, date of birth and sex were also accessed. Treatment-received information covered 6,804 people: reservation information, treatment name and date, and treatment fee.

According to the operator, the Tribeau incident included no email addresses, residential addresses, credit card information, passwords or electronic medical records. The operator also confirmed that the obtained information was not linked to case or review information, including photographs, on Tribeau. The company and the provider continue to investigate the access and its cause. Email addresses were therefore exposed in the database incident only, not in the Tribeau incident.

## Data outside the scope of the incident

As of the date of the release, the company has not confirmed that electronic medical records or information in the mySBC reservation site was acquired without authorisation. Clinical care systems and direct treatment histories fell outside the scope of the company-managed database incident. The treatment-monitor information included image file names, not the images themselves. The basic personal information category contains the fields needed to identify a person and contact them, and a reservation request, inquiry text or review can disclose a person's interest in a particular procedure.

## Email aliases after a breach

An email alias gives each service its own address, so a leak from one service exposes only the address used for that service. That address can be paused or deleted without changing the address used anywhere else. An alias does not recover data already extracted, change a password, or undo a breach. AliasFleet provides one alias per service, so a leaked alias points back to the service that leaked it.

## Protective steps for affected customers

The database incident obtained customer passwords, and the release does not state whether those passwords were hashed or stored in plain text, so the passwords are treated as compromised. [Changing a password only stops attackers if the new password is unique to that service](https://www.aliasfleet.com/blog/does-changing-your-password-stop-hackers), and the same change applies to every other service where the same password was reused: a leaked password can be tried against email, banking and shopping accounts in turn.

Exposure of an email address can be checked against breach records. A customer can check exposure with [Have I Been Pwned](https://haveibeenpwned.com), which records breaches by email address. The SBC incident is recent, so it may not appear in breach databases immediately, and an absence from the database in the first days after disclosure does not prove the address was unaffected. Anyone whose address was exposed should also [find every account linked to that email address](https://www.aliasfleet.com/blog/how-to-find-every-account-linked-to-your-email), since each account sharing the address is somewhere the leaked password may have been reused.

The leaked data hands an attacker a person's name, email address, telephone number and clinic relationship, enough to write a message that appears to come from SBC or from one of its clinics. Unexpected messages asking a customer to confirm details, pay a fee, download a form or follow a link should be checked against the clinic's published contact details rather than answered directly. The combination of [a leaked email address and password together raises the risk](https://www.aliasfleet.com/blog/email-breach-and-password-breach), because the attacker can reference real details to gain trust before asking for more.

Employees of the group and the supported medical institutions face a separate risk. Around 20,000 employee account records were obtained, and 459 employees had bank account and pension-related information affected. Those employees should change their work account passwords, check whether their work email address was exposed, and watch for targeted phishing that references their employment or payroll details.

Your address is probably in this file. [Check whether it is](https://www.aliasfleet.com/blog/how-to-check-if-your-email-was-leaked), do the password work above, and then fix the part you control: the address you hand out next time. One [AliasFleet](https://aliasfleet.com) alias per service means the next leak can only point back to the service that leaked it. [Founders Club is $7 a month, locked forever](https://aliasfleet.com/pricing), instead of $12. Early members only.

## Investigation and response

Anomalous activity was detected by SBC's security monitoring system on 16 November, and the company moved to isolate the affected server and block unauthorised access. It set up an incident response team, preserved system logs, tightened access restrictions and monitoring, and decided to commission a detailed investigation by external cybersecurity specialists. After notification from the Tribeau operator, the passwords on all accounts of the clinics to which the company provides management services on that platform were invalidated, and communications from the attacking sources were blocked.

SBC reported the database incident to Japan's Personal Information Protection Commission on 16 November and said it will take appropriate and firm action, including consulting with the police. The release states:

> "As of the date of this release, the Company has not confirmed any fraudulent use or other secondary misuse of personal information resulting from the incidents."

The method of intrusion and the full scope remain under investigation, and no attacker has been named.

The relevant medical corporations have decided to suspend television and certain other advertising for a limited period, and the company expects new patient inquiries at the affected clinics may decline during that period. SBC expects to incur costs for customer notification, call centre operations, forensic investigation, legal and advisory services, compensation and other response measures, a portion of which may be covered by cyber insurance maintained by its Japanese subsidiary, subject to policy terms and limits. The company is currently unable to reasonably estimate the financial or other impacts of the incidents, and its assessment will continue as the investigation progresses.
