2020 · Data breach

Gravatar

Breached 3 October 2020 · Published 5 December 2021 · gravatar.com

THE HUMAN IMPACT

Behind the exposed accounts

In October 2020, a security researcher published a technique for scraping large volumes of data from Gravatar, the service for providing globally unique avatars .

Follow the story
A person using a laptop beside a desktop monitor
Logan Jeffrey / Unsplash · Personal research · context photograph, not an affected user
113,990,759Accounts exposed
58/100Serious severity
3Types of data
VerifiedBy HIBP

On 3 October 2020, Gravatar was breached. 113,990,759 accounts were exposed, including email addresses, names, usernames. MyRecon rates it 58/100, serious. That is roughly everyone in Germany.

FOLLOW THE RECORD

How the story unfolded

Open a step to read the detail. Missing dates stay unknown.

  1. 01Reported breach date

    2020-10-03

    Read the HIBP source record

  2. 02Entry point

    In October 2020, a security researcher published a technique for scraping large volumes of data from Gravatar, the service for providing globally unique avatars . 167 million names, usernames and MD5 hashes of email addresses used to reference users' avatars were subsequently scraped and distributed within the hacking community.

    Read the HIBP source record

  3. 03Discovery and disclosure

    A separate discovery or company-disclosure date is not established by this feed record.

    Read the HIBP source record

  4. 04Added to the breach catalogue

    2021-12-05. This is the catalogue date, not necessarily the disclosure date.

    Read the HIBP source record

  5. 05Reported outcome

    113,990,759 accounts are listed in this breach. This is a count of accounts, not necessarily individual people. The reported exposed data includes Email addresses, Names, Usernames.

    Read the HIBP source record

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.

There is a design lesson buried in this record that outlives the incident. Gravatar identified users by the MD5 hash of their email address, published in the page source of every site that showed an avatar. The reasoning was reasonable at the time: a hash is not the address, so the address is not being disclosed.

It does not hold. MD5 is fast, email addresses follow predictable patterns, and the total space of plausible addresses is small enough to work through. Of 167 million scraped hashes, 114 million were reversed to the original address. Hashing an identifier that an attacker can guess is not anonymisation; it is a lookup table waiting to be built.

Nothing sensitive was stored and nothing was stolen in the conventional sense, this was scraping a service that was answering exactly as designed. The exposure is the mapping itself: a name, a username and the email address behind it, for a hundred million people who had only ever wanted a profile picture to follow them between websites.

The story behind the breach

In October 2020, a security researcher published a technique for scraping large volumes of data from Gravatar, the service for providing globally unique avatars . 167 million names, usernames and MD5 hashes of email addresses used to reference users' avatars were subsequently scraped and distributed within the hacking community.

114 million of the MD5 hashes were cracked and distributed alongside the source hash, thus disclosing the original email address and accompanying data. Following the impacted email addresses being searchable in HIBP, Gravatar release an FAQ detailing the incident .

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

How did it happen?

In October 2020, a security researcher published a technique for scraping large volumes of data from Gravatar, the service for providing globally unique avatars .

167 million names, usernames and MD5 hashes of email addresses used to reference users' avatars were subsequently scraped and distributed within the hacking community.

What was the motive?

The published account does not establish the motive. We cannot tell what the attackers intended from the exposed data alone.

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

What was the outcome?

113,990,759 accounts are listed in this breach. This is a count of accounts, not necessarily individual people.

The reported exposed data includes Email addresses, Names, Usernames.

What was exposed, and why it matters

Email addresses

The address becomes a confirmed, active target, expect more phishing, better aimed.

Names

Turns an anonymous address into an identified person, which is what makes targeted phishing possible.

Usernames

A handle links this account to every other place the same handle is used.

What to do if you were in it

Your next steps

Tick off the actions you have taken. Progress lasts while this page is open.

0 actions completed

Questions people ask about this breach

Was my email address in the Gravatar 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 Gravatar breach?

email addresses, names, usernames. 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 3 October 2020. It was published to Have I Been Pwned on 5 December 2021, a gap of 429 days during which the data was already out.

Is the Gravatar 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?

113,990,759 accounts. That is roughly everyone in Germany. 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