---
title: "SBC Medical website-database data theft"
description: "SBC Medical confirmed customer and employee data theft from website databases on November 16."
incident_type: "Data incident"
status: "active"
last_modified: "2026-11-19"
canonical_url: "https://www.ally.security/incidents/sbc-medical-website-database-data-theft-2026"
markdown_url: "https://www.ally.security/incidents/sbc-medical-website-database-data-theft-2026.md"
stix_url: "https://www.ally.security/incidents/sbc-medical-website-database-data-theft-2026/stix.json"
---

# SBC Medical website-database data theft

SBC Medical confirmed customer and employee data theft from website databases on November 16.

Last modified Nov 19, 2026 · 2 sources

## Summary

- **Environment:** Japanese clinic website databases
- **Operational impact:** Customer and employee information stolen; servers isolated
- **Financial impact:** No confirmed incident cost quantified

## What happened

[SBC Medical Group, Ltd.](https://sbc-holdings.com/) confirmed that an intruder extracted customer information from its Japanese website databases on November 16, 2026. [2](#source-2)

## Impact

The basic-information category covered 1,624,000 people; reservation requests, inquiries, treatment-monitor information and reviews had separate counts that must not be summed. [2](#source-2)

Employee accounts comprised about 20,000 records; employment documents affected 459 employees. [2](#source-2)

SBC said stolen customer passwords had historically been stored without encryption. [1](#source-1)

Electronic medical records and mySBC data had not been confirmed acquired. [2](#source-2)

## Timeline

### November 16, 2026 — Intrusion detected

SBC isolated the affected server. [1](#source-1)

### November 18, 2026 — Disclosure filed

SBC published its initial English account. [2](#source-2)

### November 19, 2026 — Briefing updated

This briefing was last reviewed and updated on November 19, 2026.

## Threat Group & Attack Vector

SBC described repeated external attacks but had not established the detailed intrusion method. [1](#source-1)

### Actors

- No threat actor identity is established in the reviewed evidence.

### TTPs

- No specific MITRE ATT\&CK technique is mapped for this case.

## Response

SBC isolated the server, preserved logs and reported the incident to Japan’s Personal Information Protection Commission on November 16. [2](#source-2)

It planned individual notifications and external investigation; no secondary misuse was confirmed in its notice. [1](#source-1)

## Assets

[Download the case-scoped STIX 2.1 bundle](<https://www.ally.security/incidents/sbc-medical-website-database-data-theft-2026/stix.json>)

## Sources

Primary source records used to research this incident.

<a id="source-1"></a>

### SBC Medical Group unauthorized access notice — first report

official · SBC Medical Group Holdings Incorporated · Nov 19, 2026

<https://prtimes.jp/main/html/rd/p/000000416.000097803.html>

<a id="source-2"></a>

### SBC Medical Group Reports Cybersecurity Incidents in Japan

regulatory · SBC Medical Group Holdings Incorporated · Nov 18, 2026

<https://www.sec.gov/Archives/edgar/data/1930313/000149315226053135/ex99-1.htm>

<details>
<summary>Evidence ledger</summary>

Review the supporting structured claims.

1. **Resulted In · 100% confidence · current**  
   SBC Medical website-database data theft: SBC described repeated external attacks but had not established the detailed intrusion method.
2. **Occurred At · 100% confidence · current**  
   Disclosure filed: 2026-11-18
3. **Affected Individual Count · 100% confidence · current**  
   Basic customer information: 1,624,000 individual
4. **Resulted In · 100% confidence · current**  
   Intrusion detected: SBC isolated the affected server.
5. **Resulted In · 100% confidence · current**  
   SBC Medical website-database data theft: The basic-information category covered 1,624,000 people; reservation requests, inquiries, treatment-monitor information and reviews had separate counts that must not be summed.
6. **Resulted In · 100% confidence · current**  
   Disclosure filed: SBC published its initial English account.
7. **Resulted In · 100% confidence · current**  
   SBC Medical website-database data theft: Electronic medical records and mySBC data had not been confirmed acquired.
8. **Resulted In · 100% confidence · current**  
   SBC Medical website-database data theft: It planned individual notifications and external investigation; no secondary misuse was confirmed in its notice.
9. **Resulted In · 100% confidence · current**  
   SBC Medical website-database data theft: SBC isolated the server, preserved logs and reported the incident to Japan’s Personal Information Protection Commission on November 16.
10. **Resulted In · 100% confidence · current**  
   SBC Medical website-database data theft: Employee account information
11. **Resulted In · 100% confidence · current**  
   SBC Medical website-database data theft: SBC said stolen customer passwords had historically been stored without encryption.
12. **Resulted In · 100% confidence · current**  
   SBC Medical website-database data theft: Basic customer information
13. **Resulted In · 100% confidence · current**  
   SBC Medical website-database data theft: Intrusion detected
14. **Occurred At · 100% confidence · current**  
   Intrusion detected: 2026-11-16
15. **Affected Organization · 100% confidence · current**  
   SBC Medical website-database data theft: SBC Medical Group, Ltd.
16. **Exposed Record Count · 100% confidence · current**  
   Employee account information: 20,000 record
17. **Resulted In · 100% confidence · current**  
   SBC Medical website-database data theft: Employee accounts comprised about 20,000 records; employment documents affected 459 employees.
18. **Resulted In · 100% confidence · current**  
   SBC Medical website-database data theft: SBC Medical Group, Ltd. confirmed that an intruder extracted customer information from its Japanese website databases on November 16, 2026.
19. **Resulted In · 100% confidence · current**  
   SBC Medical website-database data theft: Disclosure filed

</details>
