2026 · Data breach

CarGurus

Breached 14 February 2026 · Published 22 February 2026 · cargurus.com

THE HUMAN IMPACT

Behind the exposed accounts

In February 2026, the automotive marketplace CarGurus was the target of a data breach attributed to the threat actor ShinyHunters .

Follow the story
A person using a laptop beside a desktop monitor
Logan Jeffrey / Unsplash · Personal research · context photograph, not an affected user
12,461,887Accounts exposed
68/100Severe severity
5Types of data
VerifiedBy HIBP

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.

FOLLOW THE RECORD

How the story unfolded

Open a step to read the detail. Missing dates stay unknown.

  1. 01Reported breach date

    2026-02-14

    Read the HIBP source record

  2. 02Entry point

    The published account does not explain the exact way the data was obtained.

    Read the HIBP source record

  3. 03Discovery and disclosure

    A separate discovery or company-disclosure date is not established by this feed record.

    Read the HIBP source record

  4. 04Added to the breach catalogue

    2026-02-22. This is the catalogue date, not necessarily the disclosure date.

    Read the HIBP source record

  5. 05Reported outcome

    12,461,887 accounts are listed in this breach. This is a count of accounts, not necessarily individual people. The reported exposed data includes Email addresses, IP addresses, Names, Phone numbers, Physical addresses.

    Read the HIBP source record

Were you part of this breach?

Only a result for this incident is shown. On submission, your email is sent through MyRecon to XposedOrNot for a breach lookup. MyRecon does not save this check to your history. Provider coverage can be incomplete.

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.

The story behind the breach

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.

How did it happen?

The published account does not explain the exact way the data was obtained.

What was the motive?

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.

Reported demands or attempts to sell data describe what happened, rather than prove every attacker's intention.

What was the outcome?

12,461,887 accounts are listed in this breach. This is a count of accounts, not necessarily individual people.

The reported exposed data includes Email addresses, IP addresses, Names, Phone numbers, Physical addresses.

What was exposed, and why it matters

Email addresses

The address becomes a confirmed, active target, expect more phishing, better aimed.

IP addresses

Approximate location at the time of use, and a way to correlate accounts across services.

Names

Turns an anonymous address into an identified person, which is what makes targeted phishing possible.

Phone numbers

Enables SIM-swap attacks against SMS two-factor codes, and puts the number on scam-call lists indefinitely.

Physical addresses

Where someone actually lives. Combined with a name this moves the risk off the internet.

What to do if you were in it

Your next steps

Tick off the actions you have taken. Progress lasts while this page is open.

0 actions completed

Questions people ask about this breach

Was my email address in the CarGurus breach?

Use the email box on this page. The result applies only to this incident. If the provider does not cover this breach, we say so. A missing match does not prove you were unaffected.

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.

← All breaches