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
arrow_back Back to all breaches
Home chevron_right Recent Breaches chevron_right Victory Phones
V

Victory Phones

MEDIUM RISK

Data breach — January 2017

In January 2017, the automated telephony services company Victory Phones left a Mongo DB database publicly facing without a password. Subsequently, 213GB of data was downloaded by an unauthorised party including names, addresses, phone numbers and over 166k unique email addresses.

search Check if you were affected — free
166K
Records exposed
2017
Year of breach
6
Data types exposed
Free
To check your email

Data exposed in this breach

cakeDates of birth mailEmail addresses homeIP addresses personNames phonePhone numbers homePhysical addresses

What happened in the Victory Phones data breach?

In January 2017, the automated telephony services company Victory Phones left a Mongo DB database publicly facing without a password. Subsequently, 213GB of data was downloaded by an unauthorised party including names, addresses, phone numbers and over 166k unique email addresses.

The exposed data included 6 types of personal information. Learn more about what a data breach means for you.

Quick answer — was Victory Phones hacked?

Yes. Victory Phones was breached in January 2017. The breach exposed 166,046 records including dates of birth, 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 Victory Phones breach so dangerous?

The Victory Phones breach exposed 166,046 records — that is a large number of compromised accounts. The combination of dates of birth, email addresses, ip addresses makes this a medium-risk breach that should be addressed promptly.

Don't wait to find out — check if your email was exposed in this breach now.

What data was stolen in the Victory Phones breach?

warning

Dates of birth — used to verify identity for account takeover and fraud

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

warning

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

warning

Phone numbers — enables SIM swapping attacks and targeted SMS phishing scams

warning

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

Is the Victory Phones breach still dangerous in 2026?

Yes. Stolen data from the Victory Phones 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 2017 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 Victory Phones 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 Victory Phones breach

Approximately 166,046 user records were exposed in the Victory Phones breach in January 2017.

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

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

The Victory Phones data breach affected approximately 166,046 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 Victory Phones 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 Victory Phones breach

1

Change your Victory Phones password immediately

Go to Victory Phones 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 Victory Phones 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 Victory Phones 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 January 2017
Records 166,046
Risk level Medium
Passwords exposed No
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