advertisement

Yahoo triples the impact of its 2013 breach - to 3B accounts

BOSTON (AP) - Yahoo has tripled down on what was already the largest data breach in history, saying it affected all 3 billion accounts on its service, not the 1 billion it revealed late last year.

The company announced Tuesday that it's providing notice to additional user accounts affected by the August 2013 data theft.

The breach was previously disclosed by the company in December . The stolen information included names, email addresses, phone numbers, birthdates and security questions and answers.

Following its acquisition by Verizon in June, Yahoo says, it obtained new intelligence while investigating the breach with help from outside forensic experts. It says the stolen customer information did not include passwords in clear text, payment card data or bank account information.

Yahoo had already required users to change their passwords and invalidate security questions so they couldn't be used to hack into accounts.

"Whether it's 1 billion or 3 billion is largely immaterial. Assume it affects you," said Sam Curry, chief security officer for Boston-based firm Cybereason. "Privacy is really the victim here."

The disclosure is also a huge embarrassment for Verizon, which has just started running TV ads for its new subsidiary Oath, which will consist of Yahoo and AOL services.

FILE - In this Dec. 15, 2016, file photo, the Yahoo logo appears on a smartphone in Frankfurt, Germany. On Tuesday, Oct. 3, 2017, Yahoo tripled down on what was already the largest data breach in history, saying it affected all 3 billion of its users, not the 1 billion it revealed in late 2016. (AP Photo/Michael Probst, File) The Associated Press
Article Comments
Guidelines: Keep it civil and on topic; no profanity, vulgarity, slurs or personal attacks. People who harass others or joke about tragedies will be blocked. If a comment violates these standards or our terms of service, click the "flag" link in the lower-right corner of the comment box. To find our more, read our FAQ.