← The Breach Files

2020 · Data breach

Wattpad

Breached 29 June 2020 · Published 19 July 2020 · wattpad.com

268,765,495Accounts exposed
85/100Critical severity
11Types of data
VerifiedBy HIBP

On 29 June 2020, Wattpad was breached. 268,765,495 accounts were exposed, including bios, dates of birth, email addresses. MyRecon rates it 85/100 — critical. That is roughly everyone in Brazil.

Checked against this breach and every other on record, against public breach data only. Your address is not sent to us as a form and is not stored — it is handed straight to the lookup tool in your own browser. See the privacy policy.

The passwords were bcrypt hashes, which is the right answer and means the credential risk here is comparatively low. The exposure that matters is everything else, and it is unusually personal for a breach of this size.

Wattpad is a writing community with a young user base, and the file includes bios, dates of birth, genders, geographic locations and links to users' other social profiles. A bio is freely written text in which people describe themselves — often, at that age, more candidly than they would on any form. Combined with a date of birth and a location, it produces a record that identifies a person who was a minor at the time and says something about who they were.

That kind of data does not age out of being sensitive; it just stops being accurate. Anyone who wrote on the platform as a teenager and has since built a separate adult identity should check whether the linked social profiles in this file still connect the two.

What happened

In June 2020, the user-generated stories website Wattpad suffered a huge data breach that exposed almost 270 million records. The data was initially sold then published on a public hacking forum where it was broadly shared. The incident exposed extensive personal information including names and usernames, email and IP addresses, genders, birth dates and passwords stored as bcrypt hashes.

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

Who was behind it

No party has been publicly confirmed as responsible, and this page will not name one. Most breaches are never formally attributed: data surfaces on a forum or inside a combined dump long after the intrusion, and the trail back to a specific actor is rarely made public. Where a group has claimed responsibility it is usually named in the account above — that claim is theirs, not a finding of ours.

What was exposed, and why it matters

What to do if you were in it

  1. Change this password anywhere you reused it, starting with your email account — that is the one that can reset all the others.
  2. 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 Wattpad breach?

Enter it in the box at the top of this page. MyRecon checks it against this breach and every other one on record, and the address is never stored.

What data was leaked in the Wattpad breach?

bios, dates of birth, email addresses, genders, geographic locations, ip addresses, names, passwords, social media profiles, user website urls, 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 29 June 2020. It was published to Have I Been Pwned on 19 July 2020, a gap of 21 days during which the data was already out.

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

268,765,495 accounts. That is roughly everyone in Brazil. 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