962+ breaches tracked — check free
shield
EmailLeaked
info How it works check_circle What we check database Recent breaches help FAQ article Blog group About
search Check my email now
Privacy Terms Contact Disclaimer
arrow_back Back to all breaches
Home chevron_right Recent Breaches chevron_right Not SOCRadar
N

Not SOCRadar

MEDIUM RISK

Data breach — August 2024

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.

search Check if you were affected — free
282.5M
Records exposed
2024
Year of breach
1
Data types exposed
Free
To check your email

Data exposed in this breach

mailEmail addresses

What happened in the Not SOCRadar data breach?

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.

The exposed data included 1 types of personal information. Learn more about what a data breach means for you.

Quick answer — was Not SOCRadar hacked?

Yes. Not SOCRadar was breached in August 2024. The breach exposed 282,478,425 records including email addresses. This breach has been independently verified. If your email was involved, your data may still be at risk today. Check if you were affected.

Why was the Not SOCRadar breach so dangerous?

The Not SOCRadar breach exposed 282,478,425 records — that is 282.5M people whose personal data is now circulating on the dark web. The combination of email addresses makes this a medium-risk breach that should be addressed promptly.

Don't wait to find out — check if your email was exposed in this breach now.

What data was stolen in the Not SOCRadar breach?

warning

Email addresses — used for phishing attacks and credential stuffing against your other accounts

Is the Not SOCRadar breach still dangerous in 2026?

Yes. Stolen data from the Not SOCRadar breach remains dangerous years after the incident. Research shows that over 65% of stolen credentials from older breaches have never been changed by the account holders. Attackers routinely compile data from multiple breaches to build complete profiles, and credentials from 2024 are still actively used in credential stuffing attacks today.

Personal information like email addresses, phone numbers, and dates of birth never expire. Even if you changed your Not SOCRadar password, the other exposed data can be combined with information from other breaches to target you. Learn more about how long stolen data stays dangerous.

Frequently asked about the Not SOCRadar breach

Approximately 282,478,425 user records were exposed in the Not SOCRadar breach in August 2024.

Yes. Leaked credentials are actively used in credential stuffing attacks years after a breach. If you reused your Not SOCRadar password elsewhere and haven't changed it, those accounts remain at risk today.

Enter your email in the free checker on EmailLeaked. We scan 12 billion+ breach records including the full Not SOCRadar dataset and tell you instantly whether your email was exposed and what data was taken.

Change your Not SOCRadar password immediately, change any other account where you used the same password, enable two-factor authentication on all important accounts, and monitor for phishing emails over the next 90 days.

Who was affected by the Not SOCRadar breach?

The Not SOCRadar data breach affected approximately 282,478,425 users who had accounts with the service. With 282.5M records exposed, this is one of the larger breaches tracked in our database of 970+ known breaches.

If you ever created an account with Not SOCRadar or used their services, your data may have been included in this breach. Check your email now to find out. You can also read our guide on what to do immediately after a data breach.

If your email was in the Not SOCRadar breach

1

Change your Not SOCRadar password immediately

Go to Not SOCRadar and change your password right now. Use a strong, unique password that you have never used anywhere else.

2

Change any account sharing that password

If you used the same password on other sites, change it on every one of them. Attackers test stolen credentials on hundreds of popular sites within hours.

3

Enable two-factor authentication

Turn on 2FA on Not SOCRadar and every important account. Even if your password is known, attackers cannot get in without the second factor.

4

Check your other accounts for this breach

Run a full email check to see every breach your email appears in — not just this one.

searchCheck all my breaches — free
shield

Was your email in this breach?

Check if your email appeared in the Not SOCRadar breach and 969 other known breaches — free, instant, no signup.

search Check my email — free

No signup · Under 2 seconds · Never stored

Breach details

Breach date August 2024
Records 282,478,425
Risk level Medium
Passwords exposed No
Verified verifiedYes
View all 970+ breaches
Browse the full breach database
arrow_forward
shield

Was my email hacked?

Check if your email is compromised in seconds. Free, private, no signup. Scan 12 billion+ records across 970+ known breaches.

search Check my email now — it's free

No signup required · Results in under 5 seconds · Your data is never stored

keyboard_arrow_up
keyboard_arrow_down