MyRecon OSINT
Carhartt
On 13 August 2026, Carhartt was breached. 12,933,413 accounts were exposed, including email addresses, names, phone numbers. MyRecon rates it 67/100, severe. That is about 48% of the population of Australia.
The published corpus contained millions of synthetic records, fabricated rows matching no real person, which were identified and excluded before the figure of 12.9 million was settled on. That detail is worth more than the breach itself, because the number an extortion crew posts and the number of people actually in the file are routinely different numbers, and the first one is the one that becomes the headline.
Padding pays twice. A larger file sells for more, and a company forced to answer for an inflated figure looks worse than it is, which is useful leverage when the demand is "pay or we publish". Establishing what is actually in a dump is slow, unglamorous work, and a breach story that leads with the raw row count is a story where nobody has done it yet.
What genuinely leaked here is ordinary: name, email address, phone number, home address. No passwords, no card numbers, nothing that opens an account. That combination does not get into anything, it gets a convincing message about a delivery problem on an order you could plausibly have placed. The uptick in parcel texts after a retail breach is not a coincidence, and it is the whole return on data like this.
What happened
In August 2026, clothing retailer Carhartt was the target of a ShinyHunters "pay or leak" extortion campaign. The group subsequently published data allegedly obtained from the company including 12.9M unique email addresses, names, phone numbers and physical addresses. The published corpus also contained millions of synthetic records that did not relate to real individuals and were excluded from the breach.
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.
- 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 Carhartt 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 Carhartt breach?
email 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 13 August 2026. It was published to Have I Been Pwned on 25 August 2026, a gap of 13 days during which the data was already out.
Is the Carhartt 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,933,413 accounts. That is about 48% 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.