Breach date: 2016-05-20. Added to this index: 2016-09-13. Accounts affected: about 105K. Domain: bluesnap.com.
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 data sourced from Have I Been Pwned, used under CC BY 4.0. Additional breach metadata provided by XposedOrNot. DataExposed is an independent service and is not affiliated with or endorsed by either.
What was exposed
Browser user agent details: A short text string your browser sends to every website, naming the browser, its version, the operating system and often the device type, for example Chrome on Windows or Safari on an iPhone.
Credit card CVV: The three or four digit security code printed on your card, also called CVC or CID, which online shops ask for to show you hold the physical card.
Email addresses: The email address you used to register or log in. It is the most common field in breaches because it doubles as your username on most sites.
IP addresses: The network addresses your devices used when you signed up, logged in or posted, recorded by almost every website in its access logs.
Names: Your first name, surname and sometimes middle name or initials, as you gave them when you signed up. It appears in almost every breach because nearly every account asks for it.
Partial credit card data: Fragments of a payment card rather than the full number, typically the first six or last four digits, the card brand, the expiry date or the cardholder name.
Phone numbers: Your mobile or landline number, collected at signup for contact, delivery updates, marketing and two-factor codes.
Physical addresses: Your residential, postal, billing or delivery address, stored by retailers, utilities, banks, government services and almost any company that sends you something.
Purchases: Records of items or services you bought, often with order numbers, prices, dates, delivery addresses and the store or seller involved.
What to do now
Check whether your own address is in this dataset with the free email breach check.
Review the accounts connected to this service and turn on two-factor authentication.
Turn on two-factor authentication on your email account first, because it is the reset path for everything else.
Treat calls and messages that quote real details about you as hostile until you verify them another way.
Frequently asked questions
What data was leaked in the Regpack breach?
The Regpack breach exposed Browser user agent details, Credit card CVV, Email addresses, IP addresses, Names, Partial credit card data, Phone numbers, Physical addresses, Purchases. About 105K accounts were affected.
Was I affected by the Regpack breach?
Run the free email breach check with the address you used on that service. It will tell you whether your address appears in this dataset.
What should I do about the Regpack breach?
Treat any message that quotes details from this breach as suspicious, turn on two-factor authentication, and consider removing your details from people-search sites if your address or phone was included.