Back to Radar
BL

Regpack

Medium

Regpack breached, exposing 104,977 records with sensitive payment data.

Records exposed
104,977 records
Breach date
Breach May 20, 2016
Last update
Updated Sep 13, 2016
Source

What data was exposed?

Fields reported as compromised in this breach record.

Browser user agent detailsCredit card CVVEmail addressesIP addressesNamesPartial credit card dataPhone numbersPhysical addressesPurchases

Why does this breach matter?

In-depth analysis of the breach and its implications.

In May 2016, a data breach affected Regpack, a downstream consumer of BlueSnap's payment services. A total of 104,977 records were exposed, comprised of sensitive data such as personal information, credit card details, and payment history. The breach was traced back to a publicly accessible server misconfiguration, which the organization confirmed as human error.

Impact Analysis

Understanding the scope and consequences of this breach.

User Impact
Exposed data heightens risks of identity theft, unauthorized transactions, and phishing.
Business Impact
Regpack faced reputational damage and potential financial liabilities due to compromised user trust.
Affected Sectors
  • Payment Services
  • E-Commerce
Geographic Impact
  • Global

What You Should Do

Recommended actions to take in response to this breach.

If You Were Affected

  • •Monitor payment card statements for unauthorized transactions.
  • •Use identity theft protection services to secure personal information.
  • •Update online account credentials associated with affected data.

Preventive Measures

  • •Secure servers with proper permissions and firewalls.
  • •Conduct regular audits to identify inappropriate data access.
  • •Retain cybersecurity experts to assess and remediate vulnerabilities.

Frequently Asked Questions

Common questions about this breach and what it means for you.

The breach was due to human error leading to misconfiguration of a server, making sensitive data publicly accessible.