T2 Data Breach (2024)
Australian specialty tea retailer (Tea Too / T2) with stores in Australia, Singapore and New Zealand.
What this rating measures
The Index rates how dangerous a breach is right now rather than how large it was. It values each exposed field on its own, ages each one according to what that field is, and models what the assembled set lets an attacker do.
It is read against what is observed circulating, not what was announced. Five bands run from Low through Guarded, Elevated and High to Severe.
Every rating carries a status. Observed means it rests on fields seen circulating. Observed minimum means at least that much was seen, so read it as a floor. Provisional means the field list comes from breach catalogues and is not yet verified. How sure we are of the evidence is shown separately, and it never lowers the rating. How the Index works →
Includes a date of birth alongside enough detail to single out one person. A date of birth cannot be changed.
- Volume
- Count not yet verified
- Field types
- 8 listed
- Breach date
- Apr 2024
Breach- Listed in breach catalogues
What data was exposed
How this data can be used against you
Assessed once the record is scored.
Three key actions to take
Assume your home address is findable
Be wary of unexpected visitors, deliveries or messages that mention where you live. Ask people-search sites to remove your address, and check again every few months, because listings come back.
Change your T2 password
Change it anywhere you reused it too, and turn on two-step sign-in.
Lock your mobile number
Ask your carrier for a port-out PIN so no one can move your number to a new phone.
Check whether you were affected
Most people in a breach like this do not need an engagement. They need to know whether their address is in it, and when it turns up somewhere new. HackNotice does both, free: an Instant Check now, alerts after.
Talk to us about your exposure
If you are exposed in a way that cannot be rotated away, or you are responsible for someone who is, a call establishes what is actually reachable about you and what is worth doing first. No charge for the conversation.
Request a confidential call →The full breach analysis
What happened, what the company reported against what is circulating, the field-by-field record, the actor and the advisory.
- What happened
- Recent developments
- Reported and circulating
- Data points exposed
- Downstream risk
- Principal risk advisory
- Threat actor
- Background
- Data context
How this breach happened
In April 2024, roughly 86,000-95,000 records from the T2 tea retailer were posted to a hacking forum, with much of the data dating to 2021, and indexed by Have I Been Pwned (85,894 accounts). Exposed data included names and salutations, email and physical addresses, phone numbers, dates of birth, purchase history and passwords stored as scrypt hashes.
What has happened since the breach
In April 2024, about 86,000-95,000 T2 records were posted to a hacking forum (much of the data dating to 2021) and indexed by Have I Been Pwned (85,894 accounts). Reporting described exposure of order, wishlist and inventory files.
What was reported vs. what is circulating
Reported
- Status
- Not yet researched
Listed in breach catalogues
- Breach date
- Apr 2024
- Volume
- Count not yet verified
- Fields listed
- 8date of birth, email address, full name, password, phone number, physical address, salutation, transaction history (purchase)
The score is built only on what is listed in circulation.
Every exposed field, and how long it stays useful
| Field | Shelf life | In notice | Listed |
|---|---|---|---|
| Date of Birth | Lasts for years | No | Yes |
| Email Address | Lasts for years | No | Yes |
| Full Name | Lasts for years | No | Yes |
| Password | Expires fast | No | Yes |
| Phone Number | Fades over a few years | No | Yes |
| Physical address | Lasts for years | No | Yes |
| Salutation | Fades over a few years | No | Yes |
| Transaction History (purchase) | Lasts for years | No | Yes |
Shelf life is how long a field stays useful to someone holding it. A password expires fast. A government ID number or a date of birth lasts for years. An address stays useful long after it stops being current.
How attackers can use this data
Emails with scrypt-hashed passwords create credential-stuffing risk once cracked, especially for password reusers, while names, DOBs, addresses and purchase history support identity-verification fraud and convincing retail-themed phishing; postal addresses add mail-fraud risk. Risk compounds where these records match other breached retail or identity data.
Risks for executives and other high-profile people
A consumer-service breach: contact and account data supports phishing, account takeover and profile enrichment. For a high-profile principal this is targeting-grade, not merely identity-theft-grade: the combination lets an adversary locate, impersonate, or pressure the principal with little additional work.
Who is behind this breach
No threat actor has been publicly attributed.
About the company
T2 (registered as Tea Too) is an Australian specialty tea retailer known for a wide range of teas, teaware and accessories, operating stores across Australia, Singapore and New Zealand alongside its online shop. It is part of the Unilever group.
Why the company holds this data
As an omnichannel tea retailer, T2 holds customer records including names and salutations, email and physical addresses, phone numbers, dates of birth, purchase history and hashed (scrypt) passwords collected through online and in-store purchases and loyalty accounts.
About this record
No reported total is on record for this breach. No count has been verified for this breach yet. Figures in older breach catalogues are not shown until they are checked against the data. No score is shown until the circulating field list has been audited. Scores come from the Breach Risk Index, which rates what the exposed fields still let an attacker do, not how large the breach was. Breach records change as evidence does. If you hold a notice, a filing or a dataset observation this page does not reflect, report a correction.