Can the people behind a data breach be identified years later?
In February 2026 police in Seoul referred two teenagers to prosecutors on suspicion of a June 2024 breach of the city’s public bike-sharing service that exposed data on 4.62 million people. The case surfaced through a separate investigation, about 20 months after the breach. The report did not say what evidence linked them to it, but a breach solved late can only be investigated if the records still exist.
Sometimes, if the evidence survives. Attribution usually comes from joining up traces: the breached organisation’s logs of connections and queries, network addresses and accounts used, messages and forum posts, and links found in other investigations. Those traces can surface months or years later, and they are far easier to confirm against the breach if the organisation kept its own logs and preserved the affected systems. Keeping security logs for longer, somewhere attackers cannot alter them, and preserving evidence after any incident even when no culprit is in sight, gives investigators something to match later findings against.
What was reported
The Register reported on 24 February 2026 that the Seoul Metropolitan Police Agency had referred two teenagers to prosecutors on suspicion of violating the Information and Communications Network Act over a June 2024 breach of the city’s public bike service, which leaked data on 4.62 million people, including user IDs, phone numbers, addresses, email addresses, dates of birth, genders and weights. Police alleged that the pair “carried out the attack while still in middle school”. The Register, citing Chosun, said they were linked through evidence on devices seized in a separate investigation into a 2024 attack on another company. The report did not say what part, if any, the bike service’s own logs played. Police said they had found “no evidence the compromised data has been leaked or sold”.
They had not been tried when the report was published. They are minors; we do not identify them and draw no conclusions about them.
How attribution happens later
- Your own logs. Connections, queries and accounts recorded at the time of the breach.
- Infrastructure. Network addresses, servers and tools that reappear in other incidents.
- Communications. Messages, chat groups and posts discussing the attack, often found later on seized devices.
- Linked cases. Evidence from one investigation pointing to another.
- Matching. Comparing new findings with what the breached organisation preserved.
Without the breached organisation’s own records, linking a later lead back to the breach is much harder. Even when they survive, logs show accounts and addresses, not people, so attribution needs corroboration.
What organisations can do now
Keep security and access logs long enough to investigate incidents found late, with accurate, synchronised times, and store them where an attacker cannot change them. After any incident, preserve affected systems and logs even if no culprit is identified, and record what you kept and where. Tell the police; a report made years earlier may be what connects a later investigation to your case. 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.
See when breaches are found late and cyber investigations.
Sources
General commentary on public reports, not legal advice and not a finding about any organisation or person named in those reports. Facts are as reported at the time of writing.
Frequently asked questions
Can the people behind a data breach be identified years later?
Sometimes. Traces such as logs, network addresses, messages and links from other investigations can surface much later, and they are far easier to confirm if the breached organisation kept its logs and preserved the evidence.
Why keep logs after an incident with no known culprit?
Because a lead may surface months or years later, and preserved logs are what it can be matched against. Keep them somewhere attackers cannot alter them. The right period depends on the system and the risk; take advice.
Do logs identify the person who carried out a breach?
Not on their own. They show accounts, addresses and activity; linking those to a person usually needs other evidence.
Is it worth reporting a breach if the culprit is unknown?
Yes. A report and preserved evidence can later connect your case to another investigation.
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.
Facing something like this?
The first discussion is confidential and free, and usually changes what you decide to do next. Call +852 5808 1071 or use the case review form.