{"id":23206,"date":"2024-08-27T14:00:33","date_gmt":"2024-08-27T10:00:33","guid":{"rendered":"https:\/\/me-en.kaspersky.com\/blog\/?p=23206"},"modified":"2024-08-27T14:00:33","modified_gmt":"2024-08-27T10:00:33","slug":"top-five-data-breaches-in-history","status":"publish","type":"post","link":"https:\/\/me-en.kaspersky.com\/blog\/top-five-data-breaches-in-history\/23206\/","title":{"rendered":"RockYou2024 and the four other largest data breaches in history"},"content":{"rendered":"<p>Recent years have seen a steady <a href=\"https:\/\/www.statista.com\/statistics\/273550\/data-breaches-recorded-in-the-united-states-by-number-of-breaches-and-records-exposed\/\" target=\"_blank\" rel=\"nofollow noopener\">rise<\/a> in the amount of compromised data out there. News reports about new leaks and hacks are an almost daily occurrence, and we at Kaspersky continue to use plenty of electronic ink to tell you about the need for robust <a href=\"https:\/\/me-en.kaspersky.com\/premium?icid=me-en_bb2022-kdplacehd_acq_ona_smm__onl_b2c_kdaily_lnk_sm-team___kprem___\" target=\"_blank\" rel=\"noopener\">protection<\/a>\u00a0\u2014 now more than ever.<\/p>\n<p>Today we take a dive into history and recall (with a shudder) the biggest and baddest data breaches (DBs) of all time. To find out how much and what kind of information was leaked, who was affected, and much more besides \u2014 read on\u2026<\/p>\n<h2>1. RockYou2024<\/h2>\n<p><strong>In brief:<\/strong> hackers collected data from past leaks, and rolled out the largest-ever compilation of real user passwords: 10 billion records!<\/p>\n<p><strong>When:<\/strong> 2024.<\/p>\n<p><strong>Who was affected: <\/strong>users worldwide without <a href=\"https:\/\/me-en.kaspersky.com\/premium?icid=me-en_bb2022-kdplacehd_acq_ona_smm__onl_b2c_kdaily_lnk_sm-team___kprem___\" target=\"_blank\" rel=\"noopener\">strong protection<\/a>.<\/p>\n<p>RockYou2024 is the king of leaks, and a thorn in the side of anyone who thought hackers weren\u2019t interested in them. In July 2024, cybercriminals leaked a gigantic collection of passwords on a hacking forum: 9,948,575,739 unique records in total. Despite being a compilation based on the old RockYou2021 leak, RockYou2024 still\u2026 rocks, so to speak.<\/p>\n<p>Our expert, Alexey Antonov, analyzed the breach, and found that <strong>83% of the leaked passwords were crackable by a smart guessing algorithm in under an hour<\/strong>, with only <strong>4% of them (328 million) able to be considered strong<\/strong>: requiring over a year to crack using a smart algorithm. For details on how smart algorithms work, see our <a href=\"https:\/\/www.kaspersky.com\/blog\/password-can-be-hacked-in-one-hour\/51469\/\" target=\"_blank\" rel=\"noopener nofollow\">password strength study<\/a>, which, analyzing real user passwords leaked on the dark web, shows that far too many of us are still shockingly blas\u00e9 about password security.<\/p>\n<p>In analyzing the latest leak, Alexey filtered out all non-relevant records, and worked with the remaining array of\u2026 8.2 billion passwords <em>stored somewhere in plaintext!<\/em><\/p>\n<h2>2. CAM4<\/h2>\n<p><strong>In brief:<\/strong> a misconfigured server exposed 11 billion customer records to the public domain \u2014 sensitive information indeed given that CAM4 is\u2026 an adult site!<\/p>\n<p><strong>When:<\/strong> 2020.<\/p>\n<p><strong>Who was affected:<\/strong> users of the adult site CAM4.<\/p>\n<p>This story is of interest for two reasons: what information was leaked, and how. Among the \u201cstandard\u201d leaked details (first name, last name, email address, payment logs, etc.) was information of a far more intimate nature: gender preferences and sexual orientation. Users had to give this information at signup before they could enjoy the content of the adult streaming platform.<\/p>\n<p>The leak was caused by an insecure Elasticsearch database. However, it didn\u2019t end so badly \u2013 and embarrassingly: if we were to compile <a href=\"https:\/\/www.bleepingcomputer.com\/tag\/elasticsearch\/\" target=\"_blank\" rel=\"nofollow noopener\">all the reports of leaks related to this DB<\/a> into a physical book, we\u2019d get quite a doorstop \u2014 within which the story of CAM4 would occupy a small but important chapter: \u201cThe largest data leak in history that never was\u201d. Fortunately, the database was shut down within half-an-hour after discovering the error, and later moved to an internal local network. Users\u2019 personal data was deleted.<\/p>\n<h2>3. Yahoo<\/h2>\n<p><strong>In brief: <\/strong>A hacker attack affected all three billion users of the platform \u2014 but Yahoo admitted this only three years later.<\/p>\n<p><strong>When:<\/strong> 2012, 2013\u2026 or was it 2014? Even Yahoo doesn\u2019t know for sure.<\/p>\n<p><strong>Who was affected: <\/strong>all Yahoo users.<\/p>\n<p>More than a decade ago now, Yahoo was hacked (it all started with a phishing email), leading to a series of news stories about a rumored data leak. Initial reports mentioned a couple of hundred million hacked accounts, then that rose to around <a href=\"https:\/\/www.kaspersky.com\/blog\/possible-yahoo-password-leak\/13047\/\" target=\"_blank\" rel=\"noopener nofollow\">500 million<\/a>, then, in 2017, on the eve of the company\u2019s deal with Verizon, it turned out that all three billion accounts were affected. The hackers got hold of names, email addresses, dates of birth, and phone numbers. Even worse, they had access to the accounts of users who went years without changing their passwords. Now do you see <a href=\"https:\/\/www.kaspersky.com\/blog\/change-passwords-now\/12284\/\" target=\"_blank\" rel=\"noopener nofollow\">why it\u2019s so important to change passwords regularly and delete old profiles<\/a>?<\/p>\n<p>This incident is yet further proof that even tech giants sometimes fail to store user data properly. In the case of Yahoo, attackers found a database of unencrypted security questions and answers, and some accounts had no two-factor authentication at all. So, the moral of the story is: don\u2019t rely on social networks or online platforms to secure your personal accounts. <a href=\"https:\/\/www.kaspersky.com\/blog\/kaspersky-international-password-day-2024\/51095\/\" target=\"_blank\" rel=\"noopener nofollow\">Make up or generate strong passwords<\/a> and store them in <a href=\"https:\/\/me-en.kaspersky.com\/password-manager?icid=me-en_kdailyplacehold_acq_ona_smm__onl_b2c_kasperskydaily_wpplaceholder____kpm___\" target=\"_blank\" rel=\"noopener\">Kaspersky Password Manager<\/a>. And if you\u2019re worried your data may already have leaked, install any of <a href=\"https:\/\/me-en.kaspersky.com\/home-security?icid=me-en_kdailyplacehold_acq_ona_smm__onl_b2c_blo_lnk_sm-team______\" target=\"_blank\" rel=\"noopener\">our home security solutions<\/a>: <a href=\"https:\/\/me-en.kaspersky.com\/standard?icid=me-en_bb2022-kdplacehd_acq_ona_smm__onl_b2c_kdaily_lnk_sm-team___kstand___\" target=\"_blank\" rel=\"noopener\">Kaspersky Standard<\/a>\u00a0and <a href=\"https:\/\/me-en.kaspersky.com\/plus?icid=me-en_bb2022-kdplacehd_acq_ona_smm__onl_b2c_kdaily_lnk_sm-team___kplus___\" target=\"_blank\" rel=\"noopener\">Kaspersky Plus<\/a>\u00a0both let you specify all the email addresses that you and your family use to sign in to online services. The application regularly checks these addresses and reports any data breaches involving accounts linked to them.<\/p>\n<p>In <a href=\"https:\/\/me-en.kaspersky.com\/premium?icid=me-en_bb2022-kdplacehd_acq_ona_smm__onl_b2c_kdaily_lnk_sm-team___kprem___\" target=\"_blank\" rel=\"noopener\">Kaspersky Premium<\/a>, in addition to an email list, you can add phone numbers \u2014 these are usually used to identify users of more sensitive online services such as banking. Our application searches for these numbers and addresses in all fresh database leaks, and, if found, warns you and advises what to do (read <a href=\"https:\/\/www.kaspersky.com\/blog\/kaspersky-international-password-day-2024\/51095\/#:~:text=How%20we%20check%20your%20data\" target=\"_blank\" rel=\"noopener nofollow\">more<\/a> about how we protect you against personal data leaks online or on the dark web).<\/p>\n<h2><strong>4. UIDAI (Aadhaar)<\/strong><\/h2>\n<p><strong>In brief:<\/strong> the biometric data of almost all citizens and residents of India went up for sale.<\/p>\n<p><strong>When:<\/strong> 2018.<\/p>\n<p><strong>Who was affected: <\/strong>1.1 billion citizens and residents of India.<\/p>\n<p>The Unique Identification Authority of India (UIDAI) operates the largest bio-identification system in the world, storing the personal data, fingerprints, and iris photos of more than a billion folks in India.<\/p>\n<p>While many countries around the world are only planning to implement biometric identification, India has had such a system in place for over a decade already. UIDAI was set up so that every single resident of India would have a unique official state identity number, <a href=\"https:\/\/en.wikipedia.org\/wiki\/Aadhaar\" target=\"_blank\" rel=\"nofollow noopener\">Aadhaar<\/a>.<\/p>\n<p>But in 2018, following a string of data leaks, cybercriminals not only got their hands on the database, but <a href=\"https:\/\/www.thenewsminute.com\/news\/india-saw-world-s-largest-online-data-breach-2018-due-lax-cyber-security-wef-95141\" target=\"_blank\" rel=\"nofollow noopener\">sold it for as little as 500 rupees<\/a> (about US$6 at today\u2019s exchange rate). Another massive data breach occurred in 2023, this time <a href=\"https:\/\/logix.in\/blog\/massive-aadhaar-data-breach-exposes-personal-information-of-81-crore-indians-on-dark-web\" target=\"_blank\" rel=\"nofollow noopener\">impacting<\/a> 815 million Indians.<\/p>\n<p>Banks and law enforcement agencies continue to advise victims of the leaks to disable biometric authentication for financial services. But that\u2019s no guarantee of security, since their names, passport numbers, photos, fingerprints, and other information are likely in cybercriminal hands.<\/p>\n<h2>5. Facebook<\/h2>\n<p><strong>In brief:<\/strong> the company failed to notify users about a data breach it had known about for a full two years.<\/p>\n<p><strong>When:<\/strong> 2019.<\/p>\n<p><strong>Who was affected: <\/strong>533 million Facebook users.<\/p>\n<p>No one is surprised anymore at seeing the words \u201cFacebook\u201d and \u201cleak\u201d side by side. The platform regularly falls victim to hacker attacks and internal leaks. This particular breach \u2014 the largest in the company\u2019s history \u2014 saw the names, phone numbers, and location data of 533 million users fall into the clutches of cybercriminals. They then posted the data on a hacking forum where anyone could download it all for free. And not only regular users\u2019 account data, but that of <a href=\"https:\/\/techcrunch.com\/2021\/04\/14\/ireland-opens-gdpr-investigation-into-facebook-leak\/\" target=\"_blank\" rel=\"nofollow noopener\">public figures<\/a>, including EU Justice Commissioner Didier Reynders, and then-Prime Minister (now Foreign Minister) Xavier Bettel of Luxembourg.<\/p>\n<p>If you suspect that you too may have been hit by the Facebook data leak, use our <a href=\"https:\/\/password.kaspersky.com\" target=\"_blank\" rel=\"noopener\">Password Checker<\/a> tool to find out whether your password was compromised in this or other leaks.<\/p>\n<p>The leaked data was current for 2018\u20132019, although information about it appeared only in 2021. How did that happen? The fact is that hackers exploited the vulnerability in 2019, which <a href=\"https:\/\/x.com\/Liz_Shepherd\/status\/1378398417450377222?s=20\" target=\"_blank\" rel=\"nofollow noopener\">Facebook patched<\/a> straight away, but then forgot (or preferred not) to inform users of the incident. As a result, Meta faced more heavy criticism, plus a hefty <a href=\"https:\/\/www.theverge.com\/2022\/11\/28\/23481786\/meta-fine-facebook-data-leak-ireland-dpc-gdpr\" target=\"_blank\" rel=\"nofollow noopener\">\u20ac265 million fine<\/a> (~US$276 million in 2021).<\/p>\n<h2><strong>What do these leaks teach us?<\/strong><\/h2>\n<p>The common thread linking all these stories is: \u201cBig Tech helps those who help themselves\u201d. In other words, we are primarily responsible for the security of our data; not Facebook, not Yahoo, not even governments. <a href=\"https:\/\/me-en.kaspersky.com\/home-security?icid=me-en_kdailyplacehold_acq_ona_smm__onl_b2c_blo_lnk_sm-team______\" target=\"_blank\" rel=\"noopener\">Look after<\/a>\u00a0your accounts yourself, make up or generate strong passwords, store them in a <a href=\"https:\/\/me-en.kaspersky.com\/password-manager?icid=me-en_kdailyplacehold_acq_ona_smm__onl_b2c_kasperskydaily_wpplaceholder____kpm___\" target=\"_blank\" rel=\"noopener\">secure password manager<\/a>, and take special care when it comes to biometric data.<\/p>\n<ul>\n<li><a href=\"https:\/\/www.kaspersky.com\/blog\/never-reuse-passwords-story\/24808\/\" target=\"_blank\" rel=\"noopener nofollow\"><strong>Do not reuse passwords<\/strong><\/a><strong>.<\/strong> If you\u2019re a \u201cone password for all occasions\u201d kind of person and have been using the internet for at least a few years, we\u2019ve some bad news for you (in the link).<\/li>\n<li><a href=\"https:\/\/www.kaspersky.com\/blog\/kaspersky-international-password-day-2024\/51095\/\" target=\"_blank\" rel=\"noopener nofollow\"><strong>Check if your passwords have been compromised<\/strong><\/a><strong>. <\/strong>If you have <a href=\"https:\/\/me-en.kaspersky.com\/home-security?icid=me-en_kdailyplacehold_acq_ona_smm__onl_b2c_blo_lnk_sm-team______\" target=\"_blank\" rel=\"noopener\">our protection<\/a>, you can use our Data Leak Checker tool to enter a list of email addresses and check your user accounts. <a href=\"https:\/\/me-en.kaspersky.com\/premium?icid=me-en_bb2022-kdplacehd_acq_ona_smm__onl_b2c_kdaily_lnk_sm-team___kprem___\" target=\"_blank\" rel=\"noopener\">Kaspersky Premium<\/a>\u00a0users also have the option to check phone numbers using the Identify Theft Protection feature. The applications automatically check this information for exposure in new leaks. And in <a href=\"https:\/\/me-en.kaspersky.com\/password-manager?icid=me-en_kdailyplacehold_acq_ona_smm__onl_b2c_kasperskydaily_wpplaceholder____kpm___\" target=\"_blank\" rel=\"noopener\">our password manager<\/a>, just select Password Check from the menu, or click the key icon on the taskbar, and all stored passwords are checked for strength, uniqueness, and leaks. Everyone else can use our free <a href=\"https:\/\/password.kaspersky.com\" target=\"_blank\" rel=\"noopener\">Password Checker<\/a><\/li>\n<li><a href=\"https:\/\/www.kaspersky.com\/blog\/kaspersky-password-manager-authenticator\/48841\/\" target=\"_blank\" rel=\"noopener nofollow\"><strong>Use two-factor authentication (2FA)<\/strong><\/a> wherever possible.<\/li>\n<li><a href=\"https:\/\/www.kaspersky.com\/blog\/how-to-store-passwords-securely\/48784\/\" target=\"_blank\" rel=\"noopener nofollow\"><strong>Do not store passwords in browsers<\/strong><\/a><strong>. <\/strong>Use a <a href=\"https:\/\/me-en.kaspersky.com\/password-manager?icid=me-en_kdailyplacehold_acq_ona_smm__onl_b2c_kasperskydaily_wpplaceholder____kpm___\" target=\"_blank\" rel=\"noopener\">password manager<\/a>\u00a0to generate unique, cryptographically strong passwords for all important accounts, and then you only need <a href=\"https:\/\/www.kaspersky.com\/blog\/kaspersky-international-password-day-2024\/51095\/#:~:text=How%20to%20come%20up%20with%20a%20main%20password\" target=\"_blank\" rel=\"noopener nofollow\">think up<\/a> and remember just one \u2014 main \u2014 password that serves as the master key to all other passwords. This protects and encrypts your password vault and other vital data.<\/li>\n<\/ul>\n<input type=\"hidden\" class=\"category_for_banner\" value=\"premium-generic\">\n","protected":false},"excerpt":{"rendered":"<p>A breakdown of the most high-profile data leaks ever: from Yahoo to RockYou2024.<\/p>\n","protected":false},"author":2754,"featured_media":23207,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1225],"tags":[1449,2567,82,1183,363,97],"class_list":{"0":"post-23206","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-privacy","8":"tag-breaches","9":"tag-databases","10":"tag-hacking","11":"tag-leaks","12":"tag-personal-data","13":"tag-security-2"},"hreflang":[{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/top-five-data-breaches-in-history\/23206\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/top-five-data-breaches-in-history\/27911\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/top-five-data-breaches-in-history\/28087\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/top-five-data-breaches-in-history\/27640\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/top-five-data-breaches-in-history\/30364\/"},{"hreflang":"it","url":"https:\/\/www.kaspersky.it\/blog\/top-five-data-breaches-in-history\/29179\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/top-five-data-breaches-in-history\/38127\/"},{"hreflang":"tr","url":"https:\/\/www.kaspersky.com.tr\/blog\/top-five-data-breaches-in-history\/12767\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/top-five-data-breaches-in-history\/52040\/"},{"hreflang":"fr","url":"https:\/\/www.kaspersky.fr\/blog\/top-five-data-breaches-in-history\/22148\/"},{"hreflang":"pt-br","url":"https:\/\/www.kaspersky.com.br\/blog\/top-five-data-breaches-in-history\/22917\/"},{"hreflang":"de","url":"https:\/\/www.kaspersky.de\/blog\/top-five-data-breaches-in-history\/31619\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/top-five-data-breaches-in-history\/28224\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/top-five-data-breaches-in-history\/34020\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/top-five-data-breaches-in-history\/33682\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/me-en.kaspersky.com\/blog\/tag\/leaks\/","name":"leaks"},"_links":{"self":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/23206","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/users\/2754"}],"replies":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=23206"}],"version-history":[{"count":1,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/23206\/revisions"}],"predecessor-version":[{"id":23208,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/23206\/revisions\/23208"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/23207"}],"wp:attachment":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=23206"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=23206"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=23206"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}