{"id":15003,"date":"2014-09-10T17:08:13","date_gmt":"2014-09-10T17:08:13","guid":{"rendered":"http:\/\/kasperskydaily.com\/b2b\/?p=2547"},"modified":"2020-02-26T10:55:34","modified_gmt":"2020-02-26T15:55:34","slug":"a-large-number-of-mail-password-leaks-what-gives","status":"publish","type":"post","link":"https:\/\/www.kaspersky.com\/blog\/a-large-number-of-mail-password-leaks-what-gives\/15003\/","title":{"rendered":"A large number of mail password leaks: what gives?"},"content":{"rendered":"<p>A series of leaks were reported by Russian media, affecting local services Mail.ru and Yandex, as well as Gmail: <a href=\"https:\/\/www.cbsnews.com\/news\/russian-hackers-steal-5-million-gmail-passwords\/\" target=\"_blank\" rel=\"noopener nofollow\">a reported leak from Gmail.com<\/a> accounts for almost 5 million logins and passwords. It had been preceded with similarly massive leaks from two leading Russian free email providers \u2013 Mail.ru (over 4 million) and Yandex.ru (~1 million passwords). While not disastrous by today\u2019s \u201cstandards\u201d, it is a wake-up call for those relying on passwords alone, without any \u201cplan B\u201d for occurrences such as this one.<\/p>\n<p style=\"text-align: center\">\n<\/p><p>\u00a0<\/p>\n<p>Both Yandex and Mail.ru responded quickly, reporting that the majority of the compromised accounts are either \u201cdead\u201d or bot-created. Also, both companies insist this leak isn\u2019t a result of a single, targeted \u201cgathering\u201d operation, but rather a consequence of long-lasting malware activity on the victims\u2019 PCs. <\/p><blockquote class=\"twitter-pullquote\"><p>A large number of mail password leaks: what gives?<\/p><a href=\"https:\/\/twitter.com\/share?url=https%3A%2F%2Fkas.pr%2FM6NP&amp;text=A+large+number+of+mail+password+leaks%3A+what+gives%3F\" class=\"btn btn-twhite\" data-lang=\"en\" data-count=\"0\" target=\"_blank\" rel=\"noopener nofollow\">Tweet<\/a><\/blockquote>\n<p>\u201cWe have been aware of 85% of the compromised accounts for a long time, thanks to analysis of their behavior or some other ways,\u201d Yandex representatives said. \u201cWe have warned their owners and attempted to make them change passwords, but they haven\u2019t done it. That means that these accounts are either abandoned or created by robots.\u201d<\/p>\n<p>Similar statements were made Mail.ru, stating that the leaked passwords is the consequence of the malware activity and the victims visiting malicious sites. The company also said that 95% of the leaked accounts have been blocked ahead of the leak.<\/p>\n<p>Then there was Google\u2019s turn. Actually, the company reacted publicly <em>ahead<\/em> of the actual publication of the leaked passwords: A day before those passwords surfaced, the company warned some of its e-mail service users about an attack by the \u201cgovernment-backed hackers\u201d (It did not mention which government of which country is presumably behind this attack). Gmail has issued this kind of warnings since 2012.<\/p>\n<p style=\"text-align: center\"><a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/92\/2014\/09\/06020128\/wide-3-1.png\"><img decoding=\"async\" class=\"aligncenter size-full wp-image-2549\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/92\/2014\/09\/06020128\/wide-3-1.png\" alt=\"wide-3\" width=\"1000\" height=\"665\"><\/a><\/p>\n<p>The next day, the passwords leaked and now lots of people are taking their time checking whether they are among the affected. It is much more appropriate just to change your password ASAP.<\/p>\n<p>It doesn\u2019t seem like there is a disaster in the works: nothing like #heartbleed, for instance. But the collateral damage may be a bit larger than the direct one. The question is, whether the same passwords could be used elsewhere?<\/p>\n<p>An average Web user has to memorize up to several dozens of passwords, so it\u2019s quite tempting to use similar, or even the very same, combinations.<\/p>\n<p>And that\u2019s a Big Mistake: Crooks count on that. It\u2019s quite certain that script-kiddies are currently sifting through those \u201cmostly inactive\u201d passwords looking to use them at different resources.<\/p>\n<p>Although if they are really \u201charvested\u201d with malware, criminals already know everything \u2013 both resources and passwords.<\/p>\n<p>Passwords themselves are not an ideal protection. Even when they are a solid combination, and not something of 1234qwerty sort. Criminals have a fair amount of various \u201cpicklocks\u201d, so the passwords will be cracked if necessary. Especially if the same ones are used for years.<\/p>\n<p>But hackers will steam themselves out dealing with two-factor authentication, electronic tokens and other means of passwords reinforcement. Yeah, sure, there are Zitmo and Spitmo (By the way, what a name for a comic about two hapless clowns), stealing mTANs straight from your phone. But your phone <a href=\"https:\/\/www.kaspersky.ru\/business-security\/mobile-device-management\" target=\"_blank\" rel=\"noopener\">is already equipped with everything necessary<\/a>, isn\u2019t it? :-)<\/p>\n<blockquote class=\"twitter-pullquote\"><p>Passwords should be approached \u201creligiously\u201d: there are \u201csins\u201d and \u201cvirtues\u201d<\/p><a href=\"https:\/\/twitter.com\/share?url=https%3A%2F%2Fkas.pr%2FM6NP&amp;text=Passwords+should+be+approached+%26%238220%3Breligiously%26%238221%3B%3A+there+are+%26%238220%3Bsins%26%238221%3B+and+%26%238220%3Bvirtues%26%238221%3B\" class=\"btn btn-twhite\" data-lang=\"en\" data-count=\"0\" target=\"_blank\" rel=\"noopener nofollow\">Tweet<\/a><\/blockquote>\n<p>All in all, passwords should be approached \u201creligiously\u201d, especially in the business sphere. Appropriately, are certain \u201cdeadly sins\u201d and \u201cvirtues\u201d of the business infosec.<\/p>\n<p>Sins:<\/p>\n<ul>\n<li>1234 and asdfghj passwords<\/li>\n<li>Using the same passwords for a number of various resources<\/li>\n<li>Using the same password for more than half a year<\/li>\n<li>A yellow paper with a password written stuck to your monitor for all to see \u2013 a great sin too.<\/li>\n<\/ul>\n<p>Change your passwords and sin no more.<\/p>\n<p>And about virtues:<\/p>\n<ul>\n<li>Multifactor authentication<\/li>\n<li>Tokens<\/li>\n<li>Passwords long as an airstrip for military bombers<\/li>\n<li>Encrypted storage of the passwords<\/li>\n<\/ul>\n<p>Surely, it\u2019s a chore to memorize such combinations, but again, there are password managers that allow you to use only one password for all of the resources visited. That makes things much less painful.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A large number of logins and passwords to accounts in several free email services &#8211; Mail.ru, Yandex and Gmail.com &#8211; had been leaked. Once again, passwords prove to provide insufficient protection. What does it mean for businesses?<\/p>\n","protected":false},"author":209,"featured_media":15840,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1999,3052],"tags":[175,2178,187,1046],"class_list":{"0":"post-15003","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-business","8":"category-smb","9":"tag-gmail","10":"tag-mail-ru","11":"tag-passwords","12":"tag-yandex"},"hreflang":[{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/a-large-number-of-mail-password-leaks-what-gives\/15003\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/a-large-number-of-mail-password-leaks-what-gives\/15003\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/a-large-number-of-mail-password-leaks-what-gives\/15003\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.com\/blog\/tag\/gmail\/","name":"gmail"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/15003","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/users\/209"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=15003"}],"version-history":[{"count":4,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/15003\/revisions"}],"predecessor-version":[{"id":33315,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/15003\/revisions\/33315"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/15840"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=15003"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=15003"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=15003"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}