Social Blade Data Breach: What Was Exposed and What to Do Now
Social Blade confirmed a 2022 breach exposing emails, IP addresses, bcrypt password hashes and auth tokens across 5.6M records. It is still not listed in Have I Been Pwned.

Who was breached, what was exposed, and what to do about it.
Hashed in your browser - only five characters of the hash are ever sent.
1,000+ catalogued breaches: the date, the account count, and exactly what was exposed.
Tick what was leaked and get the steps in order, each linked to the rule behind it.
All three bureaus, plus the four registries a credit freeze does not cover.
Tips to protect your data and privacy
Browse →484 guidesBreaking news on recent data breaches
Browse →287 guidesAll the latest and largest data breaches
Browse →229 guidesIdentity theft prevention and news
Browse →203 guidesData breaches at technology companies
Browse →139 guidesData breaches affecting retail and e-commerce companies
Browse →Social Blade confirmed a 2022 breach exposing emails, IP addresses, bcrypt password hashes and auth tokens across 5.6M records. It is still not listed in Have I Been Pwned.
Understand 2026 card-fraud cases, the limits of reported-loss data, and the immediate steps that protect dispute rights.
Learn how to assess UnitedHealth breach evidence, verify a Change notice, and choose protections that match the exposed data.
Learn how bots validate stolen logins, why basic blocking falls short, and which defenses break the reuse chain.
Separate September breach disclosures reveal vendor risks, uncertain exposure, and the account checks readers should make now.
See which September retail incidents exposed sensitive records, what remains unclear, and how affected readers should respond.
Understand September’s court-vendor breach, who may be affected, and which SonicWall and Citrix fixes need attention.
Learn how to assess changed file extensions, contain a suspected attack, protect backups, and preserve evidence.
Separate the confirmed 2026 incidents from broader breach claims and choose protections based on the data actually exposed.
A prioritized control plan turns the Change Healthcare breach into concrete fixes for access, containment, recovery, and vendors.

Breach coverage goes wrong in two directions: inflating an exposure into a certainty, or burying it. We publish the disclosed numbers, name the source, and mark clearly where an investigation is still open and the count may change.

Most people find out from a letter weeks after the fact. These are the steps that still work at that point, in the order they should be done, with what each one does and does not protect.
Primary sources: the breached organization's own notification letter, filings in state Attorney General breach databases, the U.S. Department of Health and Human Services breach portal for healthcare incidents, SEC filings, court records and regulator announcements. Where we cite a figure, that figure comes from one of those documents.
Not necessarily, and the difference matters. Most notices state that an unauthorized party accessed or acquired data. That is a different finding from evidence that the data has been used for fraud. We report which one a given notice supports, and we do not fill the gap with speculation.
No. Only the organization that holds your records can confirm that, and it is required to notify you. What we can do is tell you what was disclosed, who the claims administrator or notification contact is, and what steps are worth taking while you wait.
No. Data Breach Radar is independent reporting. Nothing on this site creates a professional relationship or substitutes for advice from a lawyer, a security professional or your bank. Always verify details against the notice you received.
The site is free to read and carries advertising. Some pages may contain affiliate links, which are disclosed on our Affiliate Disclosure page. Advertisers and affiliate partners have no input into what we cover or what we say about it, and we do not accept payment to include, exclude or soften a breach report.
Email contact@databreachradar.com with the URL and what is inaccurate. Corrections to a published report are made on the page itself. Our approach to sourcing and corrections is set out in the Editorial Policy.