{"id":12211,"date":"2018-05-04T12:10:02","date_gmt":"2018-05-04T20:10:02","guid":{"rendered":"http:\/\/www.palada.net\/index.php\/2018\/05\/04\/news-5980\/"},"modified":"2018-05-04T12:10:02","modified_gmt":"2018-05-04T20:10:02","slug":"news-5980","status":"publish","type":"post","link":"http:\/\/www.palada.net\/index.php\/2018\/05\/04\/news-5980\/","title":{"rendered":"Twitter security snafu: change your passwords"},"content":{"rendered":"

Credit to Author: Christopher Boyd| Date: Fri, 04 May 2018 19:18:58 +0000<\/strong><\/p>\n

If you’re logging into Twitter after having been AWOL for a day or two, you’ll likely be seeing one of these pop-ups talking about account security:<\/p>\n

\"change<\/a><\/p>\n

Click to enlarge<\/p>\n

Don’t panic, it’s nothing that can’t be fixed.<\/p>\n

The message reads as follows:<\/p>\n

\n

Keeping your account secure<\/strong><\/em><\/p>\n

When you set a password for your Twitter account, we use technology that masks it so no one at the company can see it. We recently identified a bug that stored passwords unmasked in an internal log. We have fixed the bug, and our investigation shows no indication of breach or misuse by anyone. Out of an abundance of caution, we ask that you consider changing your password on all services where you’ve used this password<\/em><\/p>\n<\/blockquote>\n

This text is taken from a post on the official Twitter blog, where they explain what happened<\/a>\u00a0(admittedly, without a great deal of additional information), and what you should do to ward off account compromise.<\/p>\n

One slight issue I have with the notification wording is that they “ask” users to “consider” changing passwords. It feels like they should have been a lot more forceful here, or just automatically scrubbed all existing logins, making everyone update their passwords by default. Regardless of messaging, the moment a password is exposed\u2014no matter what capacity, internally or externally\u2014you owe it to yourself to go change it before things become problematic.<\/p>\n

A big issue with passwords being exposed in this kind of scenario would be a lack of two-factor authentication combined with password reuse. Not everyone makes use of 2FA, and that equals a potential threat where people reuse the same login across multiple, unrelated accounts. Thankfully, Twitter has addressed this, giving users the necessary information to do something about it.<\/p>\n

From the blog:<\/p>\n

    \n
  1. \n
    \n

    Change your password on Twitter and on any other service where you may have used the same password.<\/em><\/p>\n<\/blockquote>\n<\/li>\n

  2. \n
    \n

    Use a strong password that you don\u2019t reuse on other websites.<\/em><\/p>\n<\/blockquote>\n<\/li>\n

  3. \n
    \n

    Enable\u00a0login verification<\/a>, also known as two factor authentication. This is the single best action you can take to increase your account security.<\/em><\/p>\n<\/blockquote>\n<\/li>\n

  4. \n
    \n

    Use a password manager to make sure you\u2019re using strong, unique passwords everywhere.<\/em><\/p>\n<\/blockquote>\n<\/li>\n<\/ol>\n

    Interestingly, it appears GitHub recently ran into a similar issue with internally exposed passwords (though it doesn’t seem to be on the same scale as Twitter’s snafu):<\/p>\n

    \n

    Hi @briankrebs<\/a> I got a similar email from GitHub. I don’t know whether this too large scale as that of Twitter. pic.twitter.com\/6wWKOLG4WK<\/a><\/p>\n

    \u2014 deegovee (@deegovee) May 4, 2018<\/a><\/p>\n<\/blockquote>\n

    https:\/\/platform.twitter.com\/widgets.js<\/a><\/p>\n

    As some Twitter users have suggested, it’s possible someone at Twitter read about the GitHub incident<\/a>, checked their own logs, and then said “Oh no” a lot. However this all came about, and keeping in mind how information available to social network employees can potentially be abused<\/a>, we should be mindful that despite our best efforts as a user of a service, ultimately something can go wrong that’s entirely out of our hands. In the Twitter and GitHub cases, we strongly advise keeping passwords unique and making use of 2FA to avoid losing control of important accounts.<\/p>\n

    If you want to know more about password managers, why you might want to use them, and what ones are out there, you should check out our blog<\/a> on that very subject. Just keep in mind that sometimes incidents do happen<\/a>, and that password managers can also be\u00a0good targets for scammers<\/a>. Weigh up the pros and cons, and make the decision best suited for you personally.<\/p>\n

    If you’d like to find out about two factor authentication, then our piece on 2FA basics<\/a> will likely be just what you need. We even have some advice for what to do if you need to go on holiday<\/a> and 2FA by SMS codes won’t be available.<\/p>\n

    Finally, if you spend a lot of time on mobile Twitter, then you may wish to think about securing your mobile device, too<\/a>. All the fancy passwords in the world alongside a slice of 2FA won’t help much if someone retrieves your lost phone from a ditch and starts spamming an inventive collection of swear words and pornography links to your colleagues.<\/p>\n

    To summarize, then; login as soon as possible, change your password (and enable 2FA), take a look at your security settings<\/a>, examine your third-party applications<\/a>, and keep on Tweeting. Your social media vertical increasing can go about its business. Hooray!<\/p>\n

    The post Twitter security snafu: change your passwords<\/a> appeared first on Malwarebytes Labs<\/a>.<\/p>\n

    https:\/\/blog.malwarebytes.com\/feed\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

    Credit to Author: Christopher Boyd| Date: Fri, 04 May 2018 19:18:58 +0000<\/strong><\/p>\n\n\n\n
    <\/a><\/td>\n<\/tr>\n
    A recent error caused passwords to be exposed internally at Twitter. As a precaution, they’re advising all users to change their passwords. Read on to find out what happened, and what you can do about it.<\/p>\n

    Categories: <\/p>\n