MyRecon OSINT
Addi
On 25 March 2026, Addi was breached. 34,532,941 accounts were exposed, including age groups, credit scores, device information. MyRecon rates it 77/100 — severe. That is roughly everyone in Australia.
What happened
In March 2026, the Colombian fintech company Addi identified unauthorised activity on its platform and advised customers that "it is possible that your personal information may have been compromised". The "pay or leak" extortion group ShinyHunters subsequently claimed responsibility and published a large trove of personal data allegedly obtained from Addi. The data included 34M unique email addresses from credit scoring requests, credit bureau records, customer identity records and email validation logs. It also contained government issued IDs (Cédula de Ciudadanía), estimated income, socioeconomic levels, purchases and other credit-related data points.
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
- Age groupsAdds detail to a profile that can be assembled from several breaches at once.
- Credit scoresAdds detail to a profile that can be assembled from several breaches at once.
- Device informationFingerprints a device across services and helps an attacker imitate a trusted login.
- Email addressesThe address becomes a confirmed, active target — expect more phishing, better aimed.
- Government issued IDsPassport and licence numbers are used to prove identity to banks and telecoms, and they are effectively permanent.
- Income levelsAdds detail to a profile that can be assembled from several breaches at once.
- IP addressesApproximate location at the time of use, and a way to correlate accounts across services.
- Latitude and longitude pairsAdds detail to a profile that can be assembled from several breaches at once.
- 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.
- PurchasesWhat was bought and when — detail that makes an impersonation convincing.
- Socioeconomic levelsAdds detail to a profile that can be assembled from several breaches at once.
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.
- Consider a credit freeze. A government identifier cannot be changed, so limiting what can be opened in your name is the only real control.
- 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 Addi 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 Addi breach?
age groups, credit scores, device information, email addresses, government issued ids, income levels, ip addresses, latitude and longitude pairs, names, phone numbers, physical addresses, purchases, socioeconomic levels. 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 25 March 2026. It was published to Have I Been Pwned on 18 May 2026, a gap of 55 days during which the data was already out.
Is the Addi 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?
34,532,941 accounts. That is roughly everyone in Australia. 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.