Adult FriendFinder (2016)
HIGH RISKData breach — October 2016
In October 2016, the adult entertainment company Friend Finder Networks suffered a massive data breach. The incident impacted multiple separate online assets owned by the company, the largest of which was the Adult FriendFinder website alleged to be "the world's largest sex & swinger community". Exposed data included usernames, passwords stored as SHA-1 hashes and 170 million unique email addresses. This incident is separate to the 2015 data breach Adult FriendFinder also suffered. The data was provided to HIBP by dehashed.com.
search Check if you were affected — freeData exposed in this breach
What happened in the Adult FriendFinder (2016) data breach?
In October 2016, the adult entertainment company Friend Finder Networks suffered a massive data breach. The incident impacted multiple separate online assets owned by the company, the largest of which was the Adult FriendFinder website alleged to be "the world's largest sex & swinger community". Exposed data included usernames, passwords stored as SHA-1 hashes and 170 million unique email addresses. This incident is separate to the 2015 data breach Adult FriendFinder also suffered. The data was provided to HIBP by dehashed.com.
The exposed data included 4 types of personal information. Because passwords were exposed, users who reused their password on other sites are at particular risk. Learn more about what a data breach means for you.
Quick answer — was Adult FriendFinder (2016) hacked?
Yes. Adult FriendFinder (2016) was breached in October 2016. The breach exposed 169,746,810 records including email addresses, passwords, spoken languages. This breach has been independently verified. If your email was involved, your data may still be at risk today. Check if you were affected.
Why was the Adult FriendFinder (2016) breach so dangerous?
The Adult FriendFinder (2016) breach exposed 169,746,810 records — that is 169.7M people whose personal data is now circulating on the dark web. The combination of email addresses, passwords, spoken languages makes this a high-risk breach that requires immediate action.
Because passwords were exposed, attackers can use credential stuffing to automatically test your Adult FriendFinder (2016) password against hundreds of other websites. If you reused your password anywhere, those accounts are now at risk. Read more about what happens to your data after a breach.
Don't wait to find out — check if your email was exposed in this breach now.
What data was stolen in the Adult FriendFinder (2016) breach?
Email addresses — used for phishing attacks and credential stuffing against your other accounts
Passwords — can be used to access your accounts directly or cracked to reveal your actual password
Spoken languages — may be combined with other breach data to build a profile for targeted attacks
Usernames — used to build profiles and target you with personalised scams
Is the Adult FriendFinder (2016) breach still dangerous in 2026?
Yes. Stolen data from the Adult FriendFinder (2016) breach remains dangerous years after the incident. Research shows that over 65% of stolen credentials from older breaches have never been changed by the account holders. Attackers routinely compile data from multiple breaches to build complete profiles, and credentials from 2016 are still actively used in credential stuffing attacks today.
Personal information like email addresses, phone numbers, and dates of birth never expire. Even if you changed your Adult FriendFinder (2016) password, the other exposed data can be combined with information from other breaches to target you. Learn more about how long stolen data stays dangerous.
Frequently asked about the Adult FriendFinder (2016) breach
Approximately 169,746,810 user records were exposed in the Adult FriendFinder (2016) breach in October 2016.
Yes. Leaked credentials are actively used in credential stuffing attacks years after a breach. If you reused your Adult FriendFinder (2016) password elsewhere and haven't changed it, those accounts remain at risk today.
Enter your email in the free checker on EmailLeaked. We scan 12 billion+ breach records including the full Adult FriendFinder (2016) dataset and tell you instantly whether your email was exposed and what data was taken.
Change your Adult FriendFinder (2016) password immediately, change any other account where you used the same password, enable two-factor authentication on all important accounts, and monitor for phishing emails over the next 90 days.
Who was affected by the Adult FriendFinder (2016) breach?
The Adult FriendFinder (2016) data breach affected approximately 169,746,810 users who had accounts with the service. With 169.7M records exposed, this is one of the larger breaches tracked in our database of 970+ known breaches.
If you ever created an account with Adult FriendFinder (2016) or used their services, your data may have been included in this breach. Check your email now to find out. You can also read our guide on what to do immediately after a data breach.
If your email was in the Adult FriendFinder (2016) breach
Change your Adult FriendFinder (2016) password immediately
Go to Adult FriendFinder (2016) and change your password right now. Use a strong, unique password that you have never used anywhere else.
Change any account sharing that password
If you used the same password on other sites, change it on every one of them. Attackers test stolen credentials on hundreds of popular sites within hours.
Enable two-factor authentication
Turn on 2FA on Adult FriendFinder (2016) and every important account. Even if your password is known, attackers cannot get in without the second factor.
Check your other accounts for this breach
Run a full email check to see every breach your email appears in — not just this one.
searchCheck all my breaches — freeOther major breaches
Was my email hacked?
Check if your email is compromised in seconds. Free, private, no signup. Scan 12 billion+ records across 970+ known breaches.
search Check my email now — it's freeNo signup required · Results in under 5 seconds · Your data is never stored