Home / News / Mobile Phone News / Carphone Warehouse hack puts 2.4m customers at risk

Carphone Warehouse hack puts 2.4m customers at risk

by

carphone warehouse

Carphone Warehouse has suffered a massive cyber-attack that leaves millions of customers’ privacy at risk.

The hack, which took place on August 5, has been described as “sophisticated” by the company.

The smartphone retailer says that the personal details of up to 2.4 million Carphone Warehouse customers may have been accessed.

What’s more, 90,000 customers may have had their encrypted credit card details accessed, according to the BBC.

“We discovered that the IT systems of three of our online UK businesses had been subject to sophisticated cyber-attack,” explains Carphone Warehouse in a letter to customers.

The letter continues: “At this stage, our investigation indicates that some of the data held on our systems has been accessed and this may include some personal details, including customer name, address, date of birth, bank and encrypted card details.”

The three affected parts of the company are OneStopPhoneShop.com, e2save.com, and Mobiles.co.uk.

Carphone Warehouse also provides services to iD Mobile, TalkTalk Mobile, and Talk Mobile.

“We are, of course, informing anyone that may have been affected, and have put in place additional security measures,” says Sebastian James, chief executive at Dixons Carphone.

He adds: “We take the security of customer data extremely seriously, and we are very sorry that people have been affected by this attack on our systems.”

Related: Best Smartphones 2015

According to Carphone Warehouse, all customers who may have been affected by the attack should have received an e-mail with information and advice.

“If you have not received a communication from us regarding data security, your information should not be impacted and this message does not apply to you,” the company explains.

You can find the Carphone Warehouse FAQ on the hack by clicking on this link.

Have you received an e-mail from Carphone Warehouse or been affected by the breach? Let us know in the comments section below.

comments powered by Disqus