Facebook helps you determine whether emails really came from its servers

Posted by   Martijn Grooten on   Dec 21, 2017

There are many good reasons to criticize Facebook for its collecting of our personal data, but the company also deserves credit for being at the forefront when it comes to online security.

The company has long had a generous bug bounty program, can send PGP-encrypted notifications, and has even set up a .onion version of its website. Now the company has made it easy to determine whether a security notification that claims to have come from Facebook really was sent by its servers, or whether it might actually be a phishing or otherwise malicious email.

I've never been very happy with the advice that you should only open emails that you can be certain are genuine, and that you should check the links before clicking on them: it has resulted in phishers trying harder to make their emails and the links within them look genuine – at least to an untrained eye. A much better piece of advice is to browse directly to the site from which the email claimed to come, without clicking any links in the email, and see if you are still prompted to do whatever was apparently so urgent.

Unfortunately, it is not easy for a user be sure that the absence of any notification means that an email was fake. In fact, I would be surprised if there weren't many websites that send genuine security notifications by email without notifying you about them in your account.

To address this problem, Facebook's security settings now show all recent emails the company has sent you: if an email you have received isn't listed there, it didn't come from Facebook. And if it is listed there, it almost certainly did come from Facebook and means the link within it is safe to be clicked.

facebook_notification.png

Of course, this shouldn't stop users from setting up two-factor authentication. But it does make it really easy for the recipient to ask the perceived sender: did you really send this email? Let's hope other widely phished sites will follow Facebook's example.

twitter.png
fb.png
linkedin.png
hackernews.png
reddit.png

 

Latest posts:

New paper: Collector-stealer: a Russian origin credential and information extractor

In a new paper, F5 researchers Aditya K Sood and Rohit Chaturvedi present a 360 analysis of Collector-stealer, a Russian-origin credential and information extractor.

VB2021 localhost videos available on YouTube

VB has made all VB2021 localhost presentations available on the VB YouTube channel, so you can now watch - and share - any part of the conference freely and without registration.

VB2021 localhost is over, but the content is still available to view!

VB2021 localhost - VB's second virtual conference - took place last week, but you can still watch all the presentations.

VB2021 localhost call for last-minute papers

The call for last-minute papers for VB2021 localhost is now open. Submit before 20 August to have your paper considered for one of the slots reserved for 'hot' research!

New article: Run your malicious VBA macros anywhere!

Kurt Natvig explains how he recompiled malicious VBA macro code to valid harmless Python 3.x code.

We have placed cookies on your device in order to improve the functionality of this site, as outlined in our cookies policy. However, you may delete and block all cookies from this site and your use of the site will be unaffected. By continuing to browse this site, you are agreeing to Virus Bulletin's use of data as outlined in our privacy policy.