The Addka72424 3.3 Billion Emails Compilation is an email-only corpus posted to BreachForums on September 21, 2024, with 61,296,276 records indexed by leaksear.ch (leaksear.ch metadata). Public reporting described the wider collection as a 3.3 billion-address compilation gathered from earlier breaches and forums, rather than a newly disclosed compromise of one organization (hackerdose.com, www.cloaked.com).
What happened
The leak is best understood as a compilation incident. leaksear.ch metadata attributes the BreachForums post to the user Addka72424 and describes the source as an aggregation of email addresses from prior public data breaches and combolists (leaksear.ch metadata). HackerDose reported that the poster said the data came from public breaches and forums, while Cloaked described the set as a cleaned compilation of previous leaks (hackerdose.com, www.cloaked.com).
The BreachForums venue is relevant context for defenders. BleepingComputer reported in May 2024 that the FBI seized BreachForums, describing it as a forum used to leak and sell stolen corporate data, and The Register later reported that BreachForums returned online weeks after that takedown (www.bleepingcomputer.com, www.theregister.com).
What is confirmed for this leaksear.ch source is narrower than the public 3.3 billion label: 61,296,276 records from the corpus are indexed here, with email as the searchable field (leaksear.ch metadata).
What data was exposed
The leaksear.ch indexing metadata lists one searchable field: email (leaksear.ch metadata). No names, phone numbers, passwords, password hashes, national IDs, financial identifiers, or other stored fields are listed for this source (leaksear.ch metadata).
Public coverage of the wider compilation also characterized the dataset as primarily email addresses, with Cloaked stating that passwords were not directly included in the reported compilation (www.cloaked.com).
Why this matters
Email-only exposure can still be operationally useful to attackers because addresses are durable identifiers for phishing, spam targeting, password-reset probes, and credential-stuffing workflows when combined with older credential leaks. The risk is higher for corporate domains, reused personal addresses, and accounts that lack multifactor authentication.
Security teams should treat matches as a prompt to review phishing telemetry, watch for password-spray attempts against exposed domains, and make sure affected users are not reusing passwords tied to older breaches. Individuals who want to assess their own exposure should check the email addresses they control against this leak.
Check your exposure
Vetted researchers and incident-response teams can request access or sign in if they already have access to check this dataset. Searchable pivots for this leak include email.
Sources
- HackerDose: Hacker Leaks 3.3 Billion Emails and Yes Every Single One Is Unique
- Cloaked: 3.3 Billion Emails Exposed - Is Your Email Exposed? What Should You Do?
- BleepingComputer: FBI seize BreachForums hacking forum used to leak stolen data
- The Register: BreachForums returns just weeks after FBI-led takedown