Criticality: 8/10

Coupang’s Data Breach: Issuing $1.17 Billion in Vouchers to Impacted Customers

Source: SecurityWeek
Coupang's Data Breach: Issuing $1.17 Billion in Vouchers to Impacted Customers - Coupang data breach, data protection, purchase vouchers

The leading ecommerce giant, Coupang, has taken a proactive step to address a significant data breach that affected 33.7 million individuals. As a result, Coupang is issuing a substantial $1.17 billion worth of purchase vouchers to compensate those affected by the incident.

Background of the Incident

The breach occurred due to an internal security lapse, exposing sensitive customer data including names, email addresses, and passwords. The company has since launched a comprehensive investigation to identify the root cause and strengthen its cybersecurity measures moving forward.

Impact on Customers

Customers who were impacted by the breach can now redeem their vouchers for various products and services offered by Coupang. This initiative is aimed at mitigating the financial impact of the data breach on affected individuals.

Steps Taken by Coupang

  • Launched a detailed investigation to understand the scope and cause of the breach.
  • Implemented enhanced security protocols to prevent future incidents.
  • Provided free credit monitoring services for affected customers.
  • Contacted law enforcement agencies to report the incident.

Criticality of the Incident

The breach is considered highly critical due to the significant number of customers impacted and the sensitive nature of the data exposed. The potential financial implications for Coupang and its customers are substantial, making this a high-priority incident.

Threat Type

The threat type in this incident is primarily attributed to internal security lapses, rather than external cyberattacks or phishing attempts.

Keywords

Coupang data breach data protection purchase vouchers security measures customer compensation

Threat Type

internal security lapse

Original Source

For more information, check the original article:

View Source Article