What was exposed, when it happened, and which databases confirm it.
- accounts
- 17,745,036
- Breached
- May 10, 2020
- Last Update
- June 10, 2023
Were you caught in this breach?
Search your email, phone number or username against every record CheckLeaked indexes.
Your address never leaves this page: it is hashed in your browser and only a short fragment of that hash is sent.
What happened
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".
Compromised Info
- Email addresses
- Names
- Passwords
- Phone numbers
- Physical addresses
- Usernames
Attestation
Four independent databases catalog this breach and they do not always agree. Each lane below is one source’s own count.
1,509,263 accounts DEHASHED reports beyond HIBP
Sources & Link Methods
- LeakCheck— linked via automatic string matching
- Dehashed— linked via string match to LeakCheck
- HIBP
FAQ
What was leaked in the Zacks breach?
The Zacks breach exposed: Email addresses, Names, Passwords, Phone numbers, Physical addresses, and Usernames.
When did the Zacks breach happen?
The Zacks breach was disclosed on May 10, 2020 and affected 17,745,036 records.
Am I affected by the Zacks breach?
Search your email, phone or username at checkleaked.cc to find out whether your data appears in the Zacks leak.