Gpsunderground.com data breach

661,084 records Breach date: July 2016 no passwords

Exposed data

Email addressesNamesIP addresses

In July 2016, Gpsunderground.com suffered a data breach. The dataset indexed by LeakCheck contains 661,084 records.

The leaked records include email addresses, names and IP addresses.

The indexed records do not include passwords, but the details they hold can still be used for phishing. Run a free check below to see whether you are affected.

Check if your account is affected

Enter your email, username or phone number — the check is free and confidential, and the result will tell you whether this breach mentions you.

Exposed in this breach? Do this now

Change the password

On the breached site and everywhere else you reused it. Make every password unique.

Enable 2FA

A second factor keeps a leaked password from becoming a hijacked account.

Set up monitoring

and get notified the moment your data appears in a new leak.

Gpsunderground.com breach: questions and answers

When did the Gpsunderground.com data breach happen?

The Gpsunderground.com breach dates to July 2016.

How many records were leaked in the Gpsunderground.com breach?

LeakCheck has indexed 661,084 records from the Gpsunderground.com breach.

What data was exposed in the Gpsunderground.com breach?

The leaked records include email addresses, names and IP addresses.

Were passwords exposed in the Gpsunderground.com breach?

No. The records indexed from Gpsunderground.com do not include passwords — but the other details they hold can still be used for phishing.

How do I check if my data was in the Gpsunderground.com breach?

Enter your email address, username or phone number in the search form on this page. The free check shows whether your data appears in the Gpsunderground.com breach — and in any of the other 1,469 sources LeakCheck indexes.

What should I do if my data was in the Gpsunderground.com breach?

Change the password you used on Gpsunderground.com and everywhere you reused it, turn on two-factor authentication, and watch for phishing that quotes details from the leak. To hear about the next breach first, set up breach monitoring.