8,872,973
Records Exposed
Jun 2024
Date of Breach
Database
Breach Type
Feb 2025
Added to Database
About This Breach
In June 2024, the investment research company Zacks was allegedly breached, with the stolen data later appearing on a popular hacking forum. This incident followed a separate Zacks data breach confirmed by the organization in 2023, with the latest breach exposing millions of additional records encompassing data from the previous incident. The 2024 breach compromised 12 million unique email addresses, along with IP and physical addresses, names, usernames, phone numbers, and unsalted SHA-256 password hashes. Despite multiple attempts to contact Zacks regarding the breach, the company did not respond. This incident underscores the critical need for robust cybersecurity measures, including secure password hashing practices and timely incident response, to protect sensitive user data.
Compromised Data Types
Country
United States
Language
English
Password Storage
Other
Category
Financial
Indexed On
Feb 18, 2025
Breach Type
Database
What Should You Do?
Get Full Breach Details with LeakedSource Pro
Sign up for a LeakedSource Pro account to see exactly what data was exposed in this breach and get real-time notifications when your information appears in new breaches.
Sign Up for Pro- Change your password immediately on Zacks (2024) and any other site where you used the same password. Use a unique, strong password for each account.
- Watch for phishing emails targeting your inbox. Attackers may use your exposed email address to send convincing scam messages.
- Be alert to smishing attacks (SMS phishing). Scammers may text you pretending to be banks or service providers.
- Enable two-factor authentication (2FA) on all important accounts to add an extra layer of security.
- Use a password manager to generate and store unique, strong passwords for every account.
Were You Affected by This Breach?
Enter your email below to instantly check if your data was compromised in the Zacks (2024) breach and 12,000+ other known breaches.
