top of page

ALERT CATEGORIES

Massive CapitalOne Breach Affects Over 100 Million People

Updated: Sep 6, 2021



ALERT SUMMARY



According to CNET, a data breach to Capital One servers in March 2019 exposed the personal information of nearly 106 million of the bank's customers and applicants. The hack, which included US and Canadian customers of the banking and credit card company, followed the settlement reached between Equifax and the Federal Trade Commission concerning a hack in 2017 that affected 147 million customers.


According to Capital One, the breach on March 22 and 23, 2019, resulted in the hacker gaining access to personal information related to credit card applications from 2005 to early 2019 for consumers, applicants and small businesses. Capital One detected the breach on July 19. Among the personal data exposed were names, addresses, dates of birth, credit scores, transaction data, Social Security numbers and linked bank account numbers. 


About 140,000 Social Security numbers and 80,000 linked bank account numbers were exposed, Capital One said. And for Canadian credit card customers and applicants, approximately 1 million Social Insurance Numbers. Capital One said, however, that no credit card account numbers or login credentials were revealed in the hack.


Alert Breakdown


1. Capital One was hacked exposing more than 100 million people’s personal information.


2. The breach included 140,000 Social Security numbers and 80,000 bank account numbers, as well as one million “social insurance” numbers, which are the Canadian equivalent of Social Security numbers.


3. Customers most at risk are those who applied for credit cards after 2005. The bank has promised to make free credit monitoring and identity protection available to anyone affected by the breach.


Additional Alert Information


This means that someone could potentially use your Social Security number to open unauthorized credit accounts. Or worse, they could possibly withdraw money out of your bank account.


For additional details and step-by-step instructions on how to protect and respond to this Alert, follow the link below.




Comments


bottom of page