Gravatar — 114 Million Email Addresses Recovered From Avatar URLs (2020)
If you have an account with Gravatar, here’s what’s now in circulation.
Gravatar identifies you by the MD5 hash of your email address, published in the URL of your avatar on every site that uses it. Scraping the API yielded 167 million profiles; 114 million of those hashes were cracked back to the original addresses. Gravatar disputes that this was a breach.
What happened
In October 2020 a security researcher published a technique for scraping large volumes of data from Gravatar, the service that supplies a single globally recognised avatar across many websites. 167 million names, usernames and MD5 hashes of email addresses were subsequently scraped and distributed. 114 million of those MD5 hashes were cracked and redistributed alongside the source hash, revealing the original email address.
Gravatar's position, published after the addresses became searchable in HIBP, is that it was not hacked — the data was gathered from a public API doing what it was designed to do. That is accurate, and it is the interesting part.
The design decision at the centre of this
Gravatar works by identifying you with the MD5 hash of your email address. When a site shows your avatar, it builds an image URL containing that hash. The hash is therefore published, by design, on every page where your avatar appears — every WordPress comment, every developer forum, every profile.
MD5 is fast and unsalted, and email addresses are low-entropy: they follow predictable patterns and can be generated in bulk. Hashing a candidate list and matching against a published hash is trivially cheap. Around two thirds of the scraped hashes fell.
So there were no passwords here, and nothing to rotate. What leaked is the identifier — and unlike a password, an email address is the thing everything else is keyed on.
Why this is the identity-chain breach
Every other entry on this list gives an attacker data about a person at one site. Gravatar gives them a join key that works across every site the person commented on.
Consider what falls out. A pseudonymous commenter on a technical blog has an avatar. That avatar's URL contains the MD5 of their email. If that hash appears in the cracked set, their email address is now known — and the same hash on a different site, under a different pseudonym, proves the two accounts are the same person.
That is deanonymisation across unrelated platforms, from data the sites published voluntarily and considered harmless. For anyone who maintained separate identities across communities — which is most people with a professional life and a hobby — this is the breach that collapses them together.
What was and was not exposed
To be precise, because this incident attracts exaggeration: the exposed classes are email addresses, names and usernames. No passwords, no addresses, no payment data. The severity comes entirely from the linkage the identifier enables, not from the richness of any single record.
What to do now
What You Should Do
- Check which email address your Gravatar uses — that address is derivable from every site where your avatar appears
- Use a dedicated address for public commenting, so the join key links only your public identity
- Audit whether the same avatar appears under pseudonyms you intended to keep separate; identical avatars imply an identical email address
- Do not bother changing a password for this one — none were exposed, and the exposure is an identifier, not a credential
- Treat this as the reason to compartmentalise addresses generally: the linkage, not the leak, is the harm
What the free scan actually returns
Found on people-search siteswe remove these
These listings are live, public, and legal to remove. That’s what a Deep Sweep buys.
Found in breach recordsverifiedreported — unverified
Each record is labeled: confirmed breach data, or an attacker’s claim no one has verified.
Leaked data cannot be deleted from the internet — anyone claiming otherwise is lying. Broker listings can be removed. We do the second, and show you exactly what to fix from the first.
Report details & sourcing
Related breaches
Wattpad — 268 Million Records, and the Passwords Were the Least of It (2020)
Wattpad hashed its passwords with bcrypt, which held up. The problem is the other eleven fields: bio…
Exactis — 340 Million Records of Profiling Data Nobody Consented To (2018)
A marketing data broker left an ElasticSearch node exposed with no firewall. It held about 340 milli…
Trezor Shipping Data Breach — 13,689 Hardware Wallet Buyers, Home Addresses Included
ShipMonk, a logistics provider used by Trezor, was breached through a vulnerability in the third-par…