MyRecon OSINT
Eye4Fraud
On 25 January 2023, Eye4Fraud was breached. 16,000,591 accounts were exposed, including email addresses, ip addresses, names. MyRecon rates it 74/100 — severe. That is about 59% of the population of Australia.
What happened
In February 2023, data alleged to have been taken from the fraud protection service Eye4Fraud was listed for sale on a popular hacking forum. Spanning tens of millions of rows with 16M unique email addresses, the data was spread across 147 tables totalling 65GB and included both direct users of the service and what appears to be individuals who'd placed orders on other services that implemented Eye4Fraud to protect their sales. The data included names and bcrypt password hashes for users, and names, phone numbers, physical addresses and partial credit card data (card type and last 4 digits) for orders placed using the service. Eye4Fraud did not respond to multiple attempts to report the incident.
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.
- IP addressesApproximate location at the time of use, and a way to correlate accounts across services.
- NamesTurns an anonymous address into an identified person, which is what makes targeted phishing possible.
- Partial credit card dataNot enough to spend, but enough to convince a victim that a caller is genuinely from their bank.
- PasswordsAnyone reusing this password elsewhere has those accounts exposed too — credential stuffing is automated and tries them all within days.
- 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
- Change this password anywhere you reused it, starting with your email account — that is the one that can reset all the others.
- 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 Eye4Fraud 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 Eye4Fraud breach?
email addresses, ip addresses, 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 25 January 2023. It was published to Have I Been Pwned on 6 March 2023, a gap of 40 days during which the data was already out.
Is the Eye4Fraud 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?
16,000,591 accounts. That is about 59% of the population of 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.