How does a company work out exactly which customer data a hacker took?
In August 2026 Australia’s Origin Energy said about 900,000 current and former customers were affected by a breach, after earlier reports had put the figure at 2 million. Figures that move are often a sign of the work going on behind them: a review of exactly what was taken, from whom.
In short
By identifying exactly which systems, tables and files the attacker reached or copied, then mapping each record to a customer and each field to a type of data. That produces a per-customer view: who lost only contact details, who lost account or card fragments, and who lost identity documents or full bank details. First estimates can be too high or too low; the detailed review tests them as precisely as the evidence allows.
What was reported
The Nightly reported on 21 August 2026 that about 900,000 current and former Origin Energy customers were affected, compared with earlier reports of 2 million of its 4.8 million customers. Chief executive Frank Calabria said the hacker first contacted the company on 2 July. The exposed data included names, addresses, dates of birth, phone numbers and account information, with the last four digits of cards or last three of bank accounts; up to 15,000 people had concession or scheme numbers exposed, 60 had full bank account numbers exposed and about 100 had identity document information exposed.
The company said it had “substantially completed our review into the information accessed for each affected customer” and was offering 12 months of free credit monitoring. We draw no conclusions about the company beyond the published report.
How the per-customer review works
- Establish what was reached. From logs and system evidence, identify the databases, exports and file shares the attacker accessed, and what was copied out where that can be shown.
- Map the data. For each affected source, list the fields held: contact details, dates of birth, account numbers, card fragments, identity documents.
- Match records to people. De-duplicate across systems so each customer is counted once, and record exactly which fields were exposed for that person.
- Tier the impact. Group customers by what they lost, so that those with identity or full bank details are told first and offered the most support.
The figure that results can fall or rise. Either way it should be presented as what the evidence supports, with the assumptions stated.
Why the number matters
Notifications, regulator reports, call-centre scripts, credit monitoring and any later claims all depend on the per-customer view. Notifying everyone whose data was merely reachable, when far fewer were affected, causes needless alarm and cost; notifying too few leaves people unprotected. As at November 2026, the Personal Data (Privacy) Ordinance does not impose a general legal duty to notify the PCPD of a data breach, although the PCPD encourages notification. Sector regulators, the critical infrastructure computer systems law (Cap. 653), contracts, insurance policies and overseas laws may impose their own duties. Take legal advice on your own position.
See how access logs decide who was affected and what to do if your ID image leaked.
Sources
The Nightly, 21 Aug 2026: Origin Energy data breach
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
How does a company work out exactly which customer data a hacker took?
By establishing which systems and files the attacker reached or copied, listing the fields held in each, matching records to individual customers and recording exactly what was exposed for each person.
Why do breach numbers change after the first announcement?
Early figures may count everyone whose data was reachable, or may miss systems not yet examined. The detailed review tests this to people whose data was actually accessed or copied, as far as the evidence shows, and removes duplicates.
What if the logs cannot show what was copied?
Then the review may have to assume that everything reachable was taken, and say so. The figure is a range or an upper bound rather than an exact count.
Who should be told first after a breach?
Those whose most sensitive data, such as identity documents or full bank details, was exposed should be prioritised for support, because they face the greatest risk of misuse, without delaying notice to others.
Is breach notification required in Hong Kong?
As at November 2026, the Personal Data (Privacy) Ordinance does not impose a general legal duty to notify the PCPD of a data breach, although the PCPD encourages notification. Sector regulators, the critical infrastructure computer systems law (Cap. 653), contracts, insurance policies and overseas laws may impose their own duties. Take legal advice on your own position.
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
