Was your data in the Regpack breach?

Regpack (bluesnap.com) suffered a data breach in 2016 that exposed around 104,977 accounts. If you had an account, some of your personal data may be circulating in leaked databases. The fastest way to know is to check your own email — free, in about 30 seconds, no password required.

What happened

In July 2016, a tweet was posted with a link to an alleged data breach of BlueSnap, a global payment gateway and merchant account provider. The data contained 324k payment records across 105k unique email addresses and included personal attributes such as name, home address and phone number. The data was verified with multiple Have I Been Pwned subscribers who confirmed it also contained valid transactions, partial credit card numbers, expiry dates and CVVs. A downstream consumer of BlueSnap services known as Regpack was subsequently identified as the source of the data after they identified human error had left the transactions exposed on a publicly facing server. A full investigation of the data and statement by Regpack is detailed in the post titled Someone just lost 324k payment records, complete with CVVs.

Breach record from Have I Been Pwned, CC BY 4.0. Risk analysis by Nullivo.

What was exposed, and why it matters

Not all breaches carry the same risk — what matters is which fields leaked. Here is what the Regpack breach exposed and what each item actually enables:

Also listed in this breach: Browser user agent details, Credit card CVV, Email addresses, IP addresses, Names, Partial credit card data, Phone numbers, Physical addresses, Purchases.

What to do if you were affected

These steps are ordered for this specific breach — the most urgent action given what leaked comes first.

1. 01Payment or bank details
   Contact your bank, ask them to monitor or reissue the card, and check statements for small “test” transactions.
2. 02Home addresses
   Get your address removed from data brokers — they re-list roughly every four months, so this needs repeating.
3. 03Phone numbers
   Move two-factor authentication off SMS to an authenticator app or passkey, and add a port-out PIN with your mobile provider.
4. 04Names and usernames
   Search your usual username to see what else it exposes, and use distinct handles for sensitive accounts.
5. 05Email addresses
   Treat any message referencing this service with suspicion, and never act on links in unexpected emails.
6. 06Confirm you were actually in it
   Run a free scan before you spend time on the steps above.

This breach put your details on data-broker sites

Because Regpack exposed home addresses, this is one of the breaches that feeds people-search and data-broker sites. Those sites scrape leaked databases, combine them with public records, and republish the result as a searchable profile — which is how a single breach turns into a permanent public listing. Removal works, but brokers typically re-list within about four months, so it has to be repeated.

See our broker-by-broker removal guides →

How urgent is this now?

This breach is over 10 years old. Old credentials still cause harm — leaked passwords from a decade ago are still tried against new accounts every day.

Remember: a breach can’t be “un-leaked” — once a database is out, it exists in countless copies. The goal is to make the leaked data useless: change what can be changed, lock down what can’t, and remove what has been republished.

Frequently asked questions

Breaches that exposed similar data

If the Regpack breach affected you, these breaches exposed comparable information — worth checking too, since leaked datasets are routinely combined.

See all breaches we cover →