962+ breaches tracked — check free
shield
EmailLeaked
info How it works check_circle What we check database Recent breaches help FAQ article Blog group About
search Check my email now
Privacy Terms Contact Disclaimer
1

17

HIGH RISK

Data breach — April 2016

In April 2016, customer data obtained from the streaming app known as "17" appeared listed for sale on a Tor hidden service marketplace. The data contained over 4 million unique email addresses along with IP addresses, usernames and passwords stored as unsalted MD5 hashes.

search Check if you were affected — free
4.0M
Records exposed
2016
Year of breach
5
Data types exposed
Free
To check your email

Data exposed in this breach

infoDevice information mailEmail addresses homeIP addresses lockPasswords personUsernames

What happened in the 17 data breach?

In April 2016, customer data obtained from the streaming app known as "17" appeared listed for sale on a Tor hidden service marketplace. The data contained over 4 million unique email addresses along with IP addresses, usernames and passwords stored as unsalted MD5 hashes.

The exposed data included 5 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 17 hacked?

Yes. 17 was breached in April 2016. The breach exposed 4,009,640 records including device information, email addresses, ip addresses. 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 17 breach so dangerous?

The 17 breach exposed 4,009,640 records — that is 4.0M people whose personal data is now circulating on the dark web. The combination of device information, email addresses, ip addresses makes this a high-risk breach that requires immediate action.

Because passwords were exposed, attackers can use credential stuffing to automatically test your 17 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 17 breach?

warning

Device information — may be combined with other breach data to build a profile for targeted attacks

warning

Email addresses — used for phishing attacks and credential stuffing against your other accounts

warning

IP addresses — combined with other data, used for identity theft and physical fraud

cancel

Passwords — can be used to access your accounts directly or cracked to reveal your actual password

warning

Usernames — used to build profiles and target you with personalised scams

Is the 17 breach still dangerous in 2026?

Yes. Stolen data from the 17 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 17 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 17 breach

Approximately 4,009,640 user records were exposed in the 17 breach in April 2016.

Yes. Leaked credentials are actively used in credential stuffing attacks years after a breach. If you reused your 17 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 17 dataset and tell you instantly whether your email was exposed and what data was taken.

Change your 17 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 17 breach?

The 17 data breach affected approximately 4,009,640 users who had accounts with the service. While not the largest breach on record, it still represents a significant number of compromised accounts in our database of 970+ known breaches.

If you ever created an account with 17 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 17 breach

1

Change your 17 password immediately

Go to 17 and change your password right now. Use a strong, unique password that you have never used anywhere else.

2

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.

3

Enable two-factor authentication

Turn on 2FA on 17 and every important account. Even if your password is known, attackers cannot get in without the second factor.

4

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 — free
shield

Was your email in this breach?

Check if your email appeared in the 17 breach and 969 other known breaches — free, instant, no signup.

search Check my email — free

No signup · Under 2 seconds · Never stored

Breach details

Breach date April 2016
Records 4,009,640
Risk level High
Passwords exposed Yes
Verified verifiedYes
View all 970+ breaches
Browse the full breach database
arrow_forward
shield

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 free

No signup required · Results in under 5 seconds · Your data is never stored

keyboard_arrow_up
keyboard_arrow_down