---
title: "Sarku Japan systems incident"
description: "Sarku Japan systems incident. Parts of company systems became inaccessible."
incident_type: "Cybersecurity incident"
status: "active"
last_modified: "2026-10-30"
canonical_url: "https://www.ally.security/incidents/sarku-japan-systems-incident-2026"
markdown_url: "https://www.ally.security/incidents/sarku-japan-systems-incident-2026.md"
stix_url: "https://www.ally.security/incidents/sarku-japan-systems-incident-2026/stix.json"
---

# Sarku Japan systems incident

Sarku Japan discovered on September 7, 2026 that parts of its systems were inaccessible because of a cybersecurity incident. The company investigated, secured the affected systems and contained the incident.

Last modified Oct 30, 2026 · 1 source

## Summary

- **Environment:** Company systems and employment-related files
- **Operational impact:** Parts of company systems became inaccessible
- **Financial impact:** No confirmed incident cost quantified

## What happened

[Sarku Japan](https://www.sarkujapan.com/) discovered on September 7, 2026 that parts of its systems were inaccessible because of a cybersecurity incident. The company investigated, secured the affected systems and contained the incident. [1](#source-1)

## Impact

A review completed September 28 found personal information related to employment or engagement in affected files. The public letter leaves the specific categories as a placeholder. It does not quantify the affected population or establish the outage duration. [1](#source-1)

## Timeline

### September 7, 2026 — System disruption discovered

Sarku began investigation and containment. [1](#source-1)

### September 28, 2026 — File review completed

The review identified employment-related personal information. [1](#source-1)

### October 27, 2026 — Individual notification letter dated

The letter describes the incident and monitoring offer. The [notification sample](https://oag.ca.gov/system/files/Sarku-%20Individual%20Notification%20Letter.pdf) provides the account. [1](#source-1)

### October 30, 2026 — Briefing updated

This briefing was last reviewed and updated on October 30, 2026.

## Threat Group & Attack Vector

The notice does not identify the initial access method, an attacker or ransomware. System unavailability alone does not establish encryption or data theft. [1](#source-1)

### Actors

- No threat actor group has been identified in the reviewed public evidence.

### TTPs

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

## Response

Sarku engaged external cybersecurity and legal specialists, notified law enforcement, enhanced security and offered 12 months of credit monitoring and identity protection. [1](#source-1)

## Assets

[Download the case-scoped STIX 2.1 bundle](<https://www.ally.security/incidents/sarku-japan-systems-incident-2026/stix.json>)

## Sources

Primary source records used to research this incident.

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

### Sarasota US Topco, Inc. d/b/a Sarku Japan — notice of data incident

official · Sarasota US Topco, Inc. d/b/a Sarku Japan

<https://oag.ca.gov/system/files/Sarku-%20Individual%20Notification%20Letter.pdf>

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

Review the supporting structured claims.

1. **Resulted In · 100% confidence · current**  
   Sarku Japan systems incident: File review completed
2. **Resulted In · 100% confidence · current**  
   Sarku Japan systems incident: The notice does not identify the initial access method, an attacker or ransomware. System unavailability alone does not establish encryption or data theft.
3. **Resulted In · 100% confidence · current**  
   Sarku Japan systems incident: A review completed September 28 found personal information related to employment or engagement in affected files. The public letter leaves the specific categories as a placeholder. It does not quantify the affected population or establish the outage duration.
4. **Resulted In · 100% confidence · current**  
   Sarku Japan systems incident: Sarku Japan discovered on September 7, 2026 that parts of its systems were inaccessible because of a cybersecurity incident. The company investigated, secured the affected systems and contained the incident.
5. **Affected Organization · 100% confidence · current**  
   Sarku Japan systems incident: Sarasota US Topco, Inc. d/b/a Sarku Japan
6. **Occurred At · 100% confidence · current**  
   File review completed: 2026-09-28
7. **Resulted In · 100% confidence · current**  
   Sarku Japan systems incident: Individual notification letter dated
8. **Resulted In · 100% confidence · current**  
   Sarku Japan systems incident: System disruption discovered
9. **Occurred At · 100% confidence · current**  
   System disruption discovered: 2026-09-07
10. **Resulted In · 100% confidence · current**  
   Sarku Japan systems incident: Sarku engaged external cybersecurity and legal specialists, notified law enforcement, enhanced security and offered 12 months of credit monitoring and identity protection.
11. **Occurred At · 100% confidence · current**  
   Individual notification letter dated: 2026-10-27

</details>