MyRecon OSINT
Under Armour
On 17 November 2025, Under Armour was breached. 72,742,892 accounts were exposed, including dates of birth, email addresses, genders. MyRecon rates it 68/100 — severe. That is roughly everyone in the United Kingdom.
The size is not the interesting part. What matters here is the two-month gap: the ransomware group claimed the intrusion in November, and the data only reached a public forum in January. For anyone in that file, the exposure began long before there was anything to read about it.
That gap is the norm rather than the exception — which is why "we have seen no evidence of misuse" in a disclosure statement means considerably less than it sounds like.
What happened
In November 2025, the Everest ransomware group claimed Under Armour as a victim and attempted to extort a ransom, alleging they had obtained access to 343GB of data. In January 2026, customer data from the incident was published publicly on a popular hacking forum, including 72M email addresses. Many records also contained additional personal information such as names, dates of birth, genders, geographic locations and purchase information.
Breach description from Have I Been Pwned, used under a CC BY 4.0 licence. Data provided to HIBP by DeHashed.
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
- Dates of birthOne of the three things call centres ask to verify identity, and it never changes.
- Email addressesThe address becomes a confirmed, active target — expect more phishing, better aimed.
- GendersSmall on its own; useful to anyone assembling a fuller profile.
- Geographic locationsWhere the account was used, which narrows a person down further than most people expect.
- NamesTurns an anonymous address into an identified person, which is what makes targeted phishing possible.
- PurchasesWhat was bought and when — detail that makes an impersonation convincing.
What to do if you were in it
- 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 Under Armour 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 Under Armour breach?
dates of birth, email addresses, genders, geographic locations, names, purchases. 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 17 November 2025. It was published to Have I Been Pwned on 21 January 2026, a gap of 65 days during which the data was already out.
Is the Under Armour 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?
72,742,892 accounts. That is roughly everyone in the United Kingdom. That is accounts rather than people — one person often has several.
Read next
Also in the archive
Severity is scored by MyRecon from the number of accounts, the sensitivity of the specific fields exposed, and whether the breach is confirmed — not by a language model. The description above is quoted from Have I Been Pwned; the analysis around it is ours.