MyRecon OSINTNot SOCRadar
On 3 August 2024, Not SOCRadar was breached. 282,478,425 accounts were exposed, including email addresses. MyRecon rates it 53/100, serious. That is roughly everyone in Brazil.
The name given to this entry is the take. It is filed as Not SOCRadar because the forum post claimed a cybersecurity firm had been breached, and the investigation that followed concluded something much duller: the data had been assembled using functionality the platform openly provides, gathering from publicly available sources. No intrusion, no failure, no stolen database.
Claims made while selling something are sales copy, and a hacking forum is a marketplace. Attaching a recognisable company's name to a pile of addresses raises both the price and the attention, and the cost of the claim lands on the company, which then spends weeks proving a negative. This is why an archive that records what was established separately from what was alleged is worth more than one that repeats the post.
If your address is in this set, the proportionate response is almost nothing. It says a mailbox of yours appears in a large scraped aggregate, most likely collected from sources that were already public. No provider you trusted failed, no password is implicated, and there is nothing to reset. Expect more spam, aimed slightly better. That is the entire consequence, and pretending otherwise would be the same inflation the original post was built on.
What happened
In August 2024, over 332M rows of email addresses were posted to a popular hacking forum. The post alleged the addresses were scraped from cybersecurity firm SOCRadar, however an investigation on their behalf concluded that "the actor merely utilised functionalities inherent in the platform's standard offerings, designed to gather information from publicly available sources". There is no suggestion the incident compromised SOCRadar's security or posed any risk to their customers. In total, the data set contained 282M unique addresses of valid email address format.
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.
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 Not SOCRadar 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 Not SOCRadar breach?
email 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 3 August 2024. It was published to Have I Been Pwned on 9 August 2024, a gap of 6 days during which the data was already out.
Is the Not SOCRadar 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?
282,478,425 accounts. That is roughly everyone in Brazil. 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.