Data breaches → Regpack
Was your data in the Regpack breach?
2016 · bluesnap.com · ~104,977 accounts exposedCritical severity · 10/10
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 details sourced from Have I Been Pwned, the industry-standard breach database. 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:
Direct financial fraud, plus convincing scam calls that quote your real card or account details to establish trust.
Home addresses feed people-search and data-broker sites, which republish them publicly. They also make phishing far more convincing and, in the worst cases, enable real-world harassment.
Enables SIM-swap attacks (hijacking your number to intercept SMS codes), smishing, and voice scams that appear to come from your bank.
Links this leak to your other accounts — a reused username lets anyone build a profile of you across platforms.
Puts you on spam and phishing lists, and confirms to attackers that you hold an account with this service — which makes impersonation emails more believable.
Reveals your approximate location and internet provider, which adds credibility to targeted scams.
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.
- Payment or bank details: Contact your bank, ask them to monitor or reissue the card, and check statements for small “test” transactions.
- Home addresses: Get your address removed from data brokers — they re-list roughly every four months, so this needs repeating.
- Phone numbers: Move two-factor authentication off SMS to an authenticator app or passkey, and add a port-out PIN with your mobile provider.
- Names and usernames: Search your usual username to see what else it exposes, and use distinct handles for sensitive accounts.
- Email addresses: Treat any message referencing this service with suspicion, and never act on links in unexpected emails.
- Check whether your own email appears in this breach — run a free scan to confirm 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
What data was exposed in the Regpack breach?
The Regpack breach exposed payment or bank details, home addresses, phone numbers, names and usernames, email addresses, ip addresses. Direct financial fraud, plus convincing scam calls that quote your real card or account details to establish trust.
How many people were affected by the Regpack breach?
Around 104,977 accounts were exposed, making it a mid-sized breach.
What should I do if I had a Regpack account?
Contact your bank, ask them to monitor or reissue the card, and check statements for small “test” transactions. You can check whether your own email appears in this breach with a free Nullivo scan — no password required.
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.
- Was your data in the GoldSilver breach? (2018, ~242,715 accounts)
- Was your data in the HTH Studios breach? (2018, ~411,755 accounts)
- Was your data in the Fashion Nexus breach? (2018, ~1,279,263 accounts)
- Was your data in the ZAP-Hosting breach? (2021, ~746,682 accounts)
- Was your data in the Bonobos breach? (2020, ~2,811,929 accounts)
- Was your data in the WeLeakInfo breach? (2021, ~11,788 accounts)