2025 · Data breach

Canadian Tire

Breached 2 October 2025 · Published 25 February 2026 · canadiantire.ca

THE HUMAN IMPACT

Behind the exposed accounts

In October 2025, retailer Canadian Tire was the victim of a data breach that exposed almost 42M records.

Follow the story
A person holding a payment card while using a laptop
rupixen / Unsplash · Online payments · context photograph, not an affected customer
38,306,562Accounts exposed
77/100Severe severity
8Types of data
VerifiedBy HIBP

On 2 October 2025, Canadian Tire was breached. 38,306,562 accounts were exposed, including dates of birth, email addresses, genders. MyRecon rates it 77/100, severe. That is roughly everyone in Australia.

FOLLOW THE RECORD

How the story unfolded

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

  1. 01Reported breach date

    2025-10-02

    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-25. This is the catalogue date, not necessarily the disclosure date.

    Read the HIBP source record

  5. 05Reported outcome

    38,306,562 accounts are listed in this breach. This is a count of accounts, not necessarily individual people. The reported exposed data includes Dates of birth, Email addresses, Genders, Names, Partial credit card data, Passwords, 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.

The passwords in this one were stored as PBKDF2 hashes, which is the thing most companies in this archive got wrong and Canadian Tire got right. It is worth saying plainly, because breach coverage rarely does: a strong, slow hash means the password field is the part of this file least likely to hurt you.

The part that will is the combination underneath it. Name, date of birth, address, phone number and the card type, expiry and last four digits, all in one row. The disclosure notes that bank account information was not affected, which is true and beside the point, nobody defrauds a retail customer by knowing their account number. They do it by calling with the last four digits of the card, the correct expiry, and the customer's own date of birth, which is a script this file writes for them.

Masked card data is classified as low sensitivity because it cannot be used to transact. It can be used to be believed, and that is the attack that follows a retail breach.

The story behind the breach

In October 2025, retailer Canadian Tire was the victim of a data breach that exposed almost 42M records. The data contained 38M unique email addresses along with names, phone numbers and physical addresses. Passwords were stored as PBKDF2 hashes and for a subset of records, dates of birth and partial credit card data were also included (card type, expiry and masked card number).

In its disclosure notice , Canadian Tire advised that the incident did not impact bank account information or loyalty program data.

Breach description from Have I Been Pwned, used under a CC BY 4.0 licence.

Read the original disclosure ↗

How did it happen?

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

What was the motive?

The published account does not establish the motive. We cannot tell what the attackers intended from the exposed data alone.

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

What was the outcome?

38,306,562 accounts are listed in this breach. This is a count of accounts, not necessarily individual people.

The reported exposed data includes Dates of birth, Email addresses, Genders, Names, Partial credit card data, Passwords, Phone numbers, Physical addresses.

What was exposed, and why it matters

Dates of birth

One of the three things call centres ask to verify identity, and it never changes.

Email addresses

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

Genders

Small on its own; useful to anyone assembling a fuller profile.

Names

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

Partial credit card data

Not enough to spend, but enough to convince a victim that a caller is genuinely from their bank.

Passwords

Anyone reusing this password elsewhere has those accounts exposed too, credential stuffing is automated and tries them all within days.

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 Canadian Tire 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 Canadian Tire breach?

dates of birth, email addresses, genders, names, partial credit card data, passwords, 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 2 October 2025. It was published to Have I Been Pwned on 25 February 2026, a gap of 146 days during which the data was already out.

Is the Canadian Tire 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?

38,306,562 accounts. That is roughly everyone in 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