MyRecon OSINT
Nitro
On 28 September 2020, Nitro was breached. 77,159,696 accounts were exposed, including email addresses, names, passwords. MyRecon rates it 78/100, severe. That is roughly everyone in the United Kingdom.
The record mentions it almost in passing, and it is the most interesting thing in the entry: alongside the addresses and the bcrypt hashes, the breach exposed the titles of converted documents. Not the documents themselves. Their names.
File names are content, written by people who assumed no one else would ever read them. "Offer letter final signed", "divorce petition draft 3", "Series A term sheet", "biopsy results", "redundancy list Q4". Nobody names a private file euphemistically for their own benefit. A list of what seventy-seven million people were converting to PDF is therefore a map of what they were doing, legal trouble, job moves, medical news, deals in progress, indexed by email address and dated.
For companies that is targeting material of unusual quality: knowing an organisation converted a term sheet or a redundancy list in a particular week tells an attacker which pretext to use and exactly when to send it. For individuals it is an inference problem with no remedy. The password can be changed, and bcrypt probably held it anyway. The title of a document you converted five years ago cannot be renamed after the fact.
What happened
In September 2020, the Nitro PDF service suffered a massive data breach which exposed over 70 million unique email addresses. The breach also exposed names, bcrypt password hashes and the titles of converted documents. The data was provided to HIBP by dehashed.com.
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
- Email addressesThe address becomes a confirmed, active target, expect more phishing, better aimed.
- NamesTurns an anonymous address into an identified person, which is what makes targeted phishing possible.
- PasswordsAnyone reusing this password elsewhere has those accounts exposed too, credential stuffing is automated and tries them all within days.
What to do if you were in it
- Change this password anywhere you reused it, starting with your email account, that is the one that can reset all the others.
- 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 Nitro 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 Nitro breach?
email addresses, names, passwords. 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 28 September 2020. It was published to Have I Been Pwned on 19 January 2021, a gap of 113 days during which the data was already out.
Is the Nitro 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?
77,159,696 accounts. That is roughly everyone in the United Kingdom. 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.