← The Breach Files

2026 · Data breach

Sharecare

Breached 12 August 2026 · Published 12 October 2026 · sharecare.com

318,185Accounts exposed
59/100Serious severity
10Types of data
VerifiedBy HIBP

On 12 August 2026, Sharecare was breached. 318,185 accounts were exposed, including dates of birth, email addresses, employers. MyRecon rates it 59/100, serious.

Were you part of this breach?

Only a result for this incident is shown. On submission, your email is sent through MyRecon to XposedOrNot for a breach lookup. MyRecon does not save this check to your history. Provider coverage can be incomplete.

The story behind the breach

In August 2026, the digital health company Sharecare was the target of a ShinyHunters "pay or leak" extortion campaign . The group subsequently published data it claimed was taken from Sharecare's systems, containing 318k unique email addresses. Most of the data consisted of B2B sales and marketing records with names, physical addresses, phone numbers, job titles and employers.

The data also included a small number of Brazilian health insurance plan members, including dates of birth, genders, marital statuses and CPF numbers (Brazilian taxpayer identification numbers).

Breach description from Have I Been Pwned, used under a CC BY 4.0 licence.

How did it happen?

The published account does not explain the exact way the data was obtained.

What was the motive?

In August 2026, the digital health company Sharecare was the target of a ShinyHunters "pay or leak" extortion campaign .

Reported demands or attempts to sell data describe what happened, rather than prove every attacker's intention.

What was the outcome?

318,185 accounts are listed in this breach. This is a count of accounts, not necessarily individual people.

The reported exposed data includes Dates of birth, Email addresses, Employers, Genders, Government issued IDs, Job titles, Marital statuses, Names, Phone numbers, Physical addresses.

What was exposed, and why it matters

What to do if you were in it

  1. Move two-factor authentication off SMS and onto an authenticator app, which a SIM swap cannot intercept.
  2. Consider a credit freeze. A government identifier cannot be changed, so limiting what can be opened in your name is the only real control.
  3. Be sceptical of post and callers who already know your address, knowing it is no longer evidence of anything.
  4. Expect better-aimed phishing. A message that already knows your name and where you have an account is the whole point of a breach like this.

Questions people ask about this breach

Was my email address in the Sharecare breach?

Use the email box on this page. The result applies only to this incident. If the provider does not cover this breach, we say so. A missing match does not prove you were unaffected.

What data was leaked in the Sharecare breach?

dates of birth, email addresses, employers, genders, government issued ids, job titles, marital statuses, names, phone numbers, physical addresses. Each one is explained above, along with what it means for the person it belongs to.

When did it happen, and when did it become public?

The breach is dated 12 August 2026. It was published to Have I Been Pwned on 12 October 2026, a gap of 62 days during which the data was already out.

Is the Sharecare breach real?

Yes. Have I Been Pwned lists it as verified, meaning the data was checked against the source rather than taken on trust.

How many people were affected?

318,185 accounts. That is accounts rather than people, one person often has several.

Read next

Also in the archive

Case Files: how the landmark breaches actually happened →

Three kinds of content appear on this page and they are kept apart deliberately. The breach description is quoted from Have I Been Pwned under its licence. The severity score, the field-by-field explanation and the advice are computed from the record itself, every sentence derives from a number or a flag in it, which is what stops the analysis drifting from the evidence. Anything under the "MyRecon's take" byline is editorial: our reading of this breach, presented as opinion rather than as a finding.

← All breaches