Zacks
HIGH RISKData breach — May 2020
In December 2022, the investment research company Zacks announced a data breach. The following month, reports emerged of the incident impacting 820k customers. However, in June 2023, a corpus of data with almost 9M Zacks customers appeared before being broadly circulated on a popular hacking forum. The most recent data was dated May 2020 and included names, usernames, email and physical addresses, phone numbers and passwords stored as unsalted SHA-256 hashes. On disclosure of the larger breach, Zacks advised that in addition to their original report "the unauthorised third parties also gained access to encrypted [sic] passwords of zacks.com customers, but only in the encrypted [sic] format".
search Check if you were affected — freeData exposed in this breach
What happened in the Zacks data breach?
In December 2022, the investment research company Zacks announced a data breach. The following month, reports emerged of the incident impacting 820k customers. However, in June 2023, a corpus of data with almost 9M Zacks customers appeared before being broadly circulated on a popular hacking forum. The most recent data was dated May 2020 and included names, usernames, email and physical addresses, phone numbers and passwords stored as unsalted SHA-256 hashes. On disclosure of the larger breach, Zacks advised that in addition to their original report "the unauthorised third parties also gained access to encrypted [sic] passwords of zacks.com customers, but only in the encrypted [sic] format".
The exposed data included 6 types of personal information. Because passwords were exposed, users who reused their password on other sites are at particular risk. Learn more about what a data breach means for you.
Quick answer — was Zacks hacked?
Yes. Zacks was breached in May 2020. The breach exposed 8,929,503 records including email addresses, names, passwords. 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 Zacks breach so dangerous?
The Zacks breach exposed 8,929,503 records — that is 8.9M people whose personal data is now circulating on the dark web. The combination of email addresses, names, passwords makes this a high-risk breach that requires immediate action.
Because passwords were exposed, attackers can use credential stuffing to automatically test your Zacks password against hundreds of other websites. If you reused your password anywhere, those accounts are now at risk. Read more about what happens to your data after a breach.
Don't wait to find out — check if your email was exposed in this breach now.
What data was stolen in the Zacks breach?
Email addresses — used for phishing attacks and credential stuffing against your other accounts
Names — used to build profiles and target you with personalised scams
Passwords — can be used to access your accounts directly or cracked to reveal your actual password
Phone numbers — enables SIM swapping attacks and targeted SMS phishing scams
Physical addresses — combined with other data, used for identity theft and physical fraud
Usernames — used to build profiles and target you with personalised scams
Is the Zacks breach still dangerous in 2026?
Yes. Stolen data from the Zacks 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 2020 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 Zacks 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 Zacks breach
Approximately 8,929,503 user records were exposed in the Zacks breach in May 2020.
Yes. Leaked credentials are actively used in credential stuffing attacks years after a breach. If you reused your Zacks 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 Zacks dataset and tell you instantly whether your email was exposed and what data was taken.
Change your Zacks 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 Zacks breach?
The Zacks data breach affected approximately 8,929,503 users who had accounts with the service. While not the largest breach on record, it still represents a significant number of compromised accounts in our database of 970+ known breaches.
If you ever created an account with Zacks 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 Zacks breach
Change your Zacks password immediately
Go to Zacks and change your password right now. Use a strong, unique password that you have never used anywhere else.
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.
Enable two-factor authentication
Turn on 2FA on Zacks and every important account. Even if your password is known, attackers cannot get in without the second factor.
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 — freeOther major breaches
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 freeNo signup required · Results in under 5 seconds · Your data is never stored