What happens when a cyber attack hits several companies in the same group?
In January 2026 The Korea Times reported a suspected ransomware attack on Kyowon Group affecting eight affiliates, with about 9.6 million accounts potentially affected. The report said that figure counted people with more than one account, and that the affiliates’ 13 million members came to 5.54 million once overlaps were removed. When an attack crosses several companies in a group, working out which company holds which data, and for whom, becomes part of the investigation.
In short
The investigation is usually best run as one, but its findings usually need to be set out company by company. Each affiliate may be a separate organisation with its own customers, contracts and any legal obligations, even if they share servers, networks and staff. Investigators map which systems each company uses and shares, work out the scope of the attack across all of them, then establish, for each company, what data may have been affected and for how many people, removing duplicates where the same person is a customer of several affiliates. Counting accounts and counting people give different numbers, and both may matter.
What was reported
The Korea Times, carrying Yonhap, reported on 14 January 2026 that Kyowon Group had found unusual activity and reported a possible breach, citing signs of a ransomware attack. It said eight affiliates were affected, including tutoring, home appliance rental and funeral services, and that a government team estimated that 600 of the company’s 800 servers fell within the scope of the breach. About 9.6 million accounts might be affected; the affiliates had 13 million members, or 5.54 million after removing overlaps, and “the 9.6-million estimate counts users holding more than one account”.
The report said a leak had not been confirmed and that Kyowon was working “to determine whether consumers’ data was actually breached”. We draw no conclusions about the company.
What makes a group incident harder
- Shared systems. Networks, servers, accounts and administrators shared across companies let an attacker move between them.
- Separate obligations. Each company may owe its own customers, regulators and contracts.
- Duplicate people. The same person may hold accounts with several affiliates, so totals can overstate or understate who is affected.
- Different records. Each company may log differently, or keep logs for different periods.
- One voice. Group and affiliate statements need to agree with each other and with the evidence.
Preparing before it happens
Keep an up-to-date map of which systems, databases and administrator accounts each group company uses and shares. Agree in advance who leads an incident, how findings will be reported for each company, and who takes advice on each company’s obligations. Keep logs for each company long enough to investigate, and in a form that can be compared. On reporting duties in Hong Kong, see the FAQ below.
See working out which customer data was taken and cyber investigations.
Sources
This article is general commentary on public reports, not legal advice and not a finding about any organisation named in those reports. Facts are as reported at the time of writing.
Frequently asked questions
What happens when a cyber attack hits several companies in the same group?
The investigation is usually best run as one, but findings usually need to be set out company by company, because each affiliate may have its own customers and obligations. Investigators map shared systems, scope the attack across all of them, and establish what each company's data exposure is.
Why do breach figures count accounts rather than people?
Systems record accounts, and one person may hold several, so the number of people affected can be lower than the number of accounts. In the Kyowon report, about 9.6 million accounts might be affected, and that estimate counted people with more than one account; the affiliates had 13 million members, or 5.54 million after removing overlaps.
Does each group company have to report separately?
It may. Each company can be a separate organisation with its own obligations. Take advice for each one.
Do Hong Kong organisations have to report a breach?
As at November 2026 there is no general legal duty under the PDPO to notify the PCPD of a data breach, although the PCPD encourages notification. Under Cap. 653, only designated critical infrastructure operators (designated organisations are notified in writing; the list is not published) must report computer security incidents affecting their critical computer systems: within 12 hours of becoming aware of a serious incident, and within 48 hours of becoming aware of any other incident. Other laws may apply. Take advice.
How can a group prepare for a shared cyber attack?
Keep a map of shared systems and accounts, agree who leads an incident and how findings are reported for each company, and keep comparable logs for long enough to investigate.
Talk to us before anything is changed.
A short, confidential call is usually enough to tell you what to preserve, what it will cost and whether a forensic examination is worthwhile. We take instructions from solicitors, companies and individuals in Hong Kong and across the Asia-Pacific region.
Telephone +852 5808 1071 · Signal or WhatsApp +852 9103 1852 · Email enquiries@d3forensics.com · Enquiry form
