CarGurus
On 14 February 2026, CarGurus was breached. 12,461,887 accounts were exposed, including email addresses, ip addresses, names. MyRecon rates it 68/100, severe. That is about 46% of the population of Australia.
One phrase in the field list deserves a stop: finance pre-qualification application data. Those are people who asked a car marketplace what they could borrow, a question nobody asks idly, and the answer is sitting beside their name, phone number and home address.
Intent is the part of a breach that rarely makes the summary and reliably makes the fraud. Knowing that someone is shopping for a car, and roughly what they can finance, tells a caller which pretext will land: a rate they have been approved for, a deposit to hold a vehicle, a dealer following up on the application they really did fill in last week. Generic scams get hung up on. This one continues a conversation the victim started.
Dealer account and subscription records were in the same release, which hands the same caller both ends of that conversation, the buyer's details and a real dealership to impersonate. The defence is procedural rather than technical: anything about a vehicle purchase, a finance offer or a deposit gets confirmed by ringing the dealer on a number you looked up yourself. Never the number in the message, however well the message knows you.
What happened
In February 2026, the automotive marketplace CarGurus was the target of a data breach attributed to the threat actor ShinyHunters. Following an attempted extortion, the data was published publicly and contained more than 12M email addresses across multiple files including user account ID mappings, finance pre-qualification application data and dealer account and subscription information. Impacted data also included names, phone numbers, physical and IP addresses, and auto finance application outcomes.
Breach description from Have I Been Pwned, used under a CC BY 4.0 licence.
Who was behind it
No party has been publicly confirmed as responsible, and this page will not name one. Most breaches are never formally attributed: data surfaces on a forum or inside a combined dump long after the intrusion, and the trail back to a specific actor is rarely made public. Where a group has claimed responsibility it is usually named in the account above, that claim is theirs, not a finding of ours.
What was exposed, and why it matters
- Email addressesThe address becomes a confirmed, active target, expect more phishing, better aimed.
- IP addressesApproximate location at the time of use, and a way to correlate accounts across services.
- NamesTurns an anonymous address into an identified person, which is what makes targeted phishing possible.
- Phone numbersEnables SIM-swap attacks against SMS two-factor codes, and puts the number on scam-call lists indefinitely.
- Physical addressesWhere someone actually lives. Combined with a name this moves the risk off the internet.
What to do if you were in it
- Move two-factor authentication off SMS and onto an authenticator app, which a SIM swap cannot intercept.
- Be sceptical of post and callers who already know your address, knowing it is no longer evidence of anything.
- Expect better-aimed phishing. A message that already knows your name and where you have an account is the whole point of a breach like this.
Questions people ask about this breach
Was my email address in the CarGurus breach?
Enter it in the box at the top of this page. MyRecon checks it against this breach and every other one on record, and the address is never stored.
What data was leaked in the CarGurus breach?
email addresses, ip addresses, names, phone numbers, physical addresses. Each one is explained above, along with what it means for the person it belongs to.
When did it happen, and when did it become public?
The breach is dated 14 February 2026. It was published to Have I Been Pwned on 22 February 2026, a gap of 8 days during which the data was already out.
Is the CarGurus breach real?
Yes. Have I Been Pwned lists it as verified, meaning the data was checked against the source rather than taken on trust.
How many people were affected?
12,461,887 accounts. That is about 46% of the population of Australia. That is accounts rather than people, one person often has several.
Read next
Also in the archive
Case Files: how the landmark breaches actually happened →
Three kinds of content appear on this page and they are kept apart deliberately. The breach description is quoted from Have I Been Pwned under its licence. The severity score, the field-by-field explanation and the advice are computed from the record itself, every sentence derives from a number or a flag in it, which is what stops the analysis drifting from the evidence. Anything under the "MyRecon's take" byline is editorial: our reading of this breach, presented as opinion rather than as a finding.