Commentary

David Berlind
 

InformationWeek Editor Duped In Facebook Phishing Scam

The damage could have been worse. I had my guard down. Although today started like any other day, I hadn't even taken one sip of my tea when I noticed a slight hiccup to the way things normally work when logging into Facebook (see image below). And now, someone out there (I'm not sure who) has the password I used to use for Facebook as well as for a handful of other sites. It's one of my not-to-be-used-for-transactional (financial)-sites passwords. So, nothing serious is at risk and I think I moved fast enough to go so far as to say nothing is at risk. But I should have known better and you can learn from my mistake.

The damage could have been worse. I had my guard down. Although today started like any other day, I hadn't even taken one sip of my tea when I noticed a slight hiccup to the way things normally work when logging into Facebook (see image below). And now, someone out there (I'm not sure who) has the password I used to use for Facebook as well as for a handful of other sites. It's one of my not-to-be-used-for-transactional (financial)-sites passwords. So, nothing serious is at risk and I think I moved fast enough to go so far as to say nothing is at risk. But I should have known better and you can learn from my mistake.If you're currently a Facebook user, then the e-mail message below should look familiar. As can be seen from the image, the message that Jessica Lamoureux had written on my wall looks exactly like the hundreds of other messages that Facebook fills my in-box with.

I missed the fact that it was sent to my TechWeb address, which is not the e-mail address of record for my Facebook account. I also didn't bother to do what I usually do with links in e-mail messages (before clicking on them); I didn't mouse-over the message to double-check that the URI being displayed in the message wasn't an imposter that was masking a non-Facebook URL. As can be seen from below, it was. I also missed that once I clicked through, the URL in Firefox was pointing to http://facesbookcom.awardspace.com. I was asleep at the keyboard.


More Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

But the site's behavior certainly got my attention. I went through what appeared to be a normal login process, but then was asked for my password again. This second password request came from a legitimate Facebook page to which the imposter had redirected me. It's brilliant because if you're not paying close attention, you end up logged in to your actual Facebook account and may never realize that something was amiss. But I also was expecting to be taken directly to Miss Lamoureux' message (as is the normal behavior when clicking through e-mail) and that didn't happen. But by the time my spider senses were tingling, the "phishers" had both my login ID as well as my password. It happens to the best of us.

As I said earlier, the damage could have been worse. For example, by the time I realized my mistake, two key pieces of information on my Facebook account remained unchanged: my password and the contact e-mail. I changed both immediately. The phisher might have had some automated systems in place to change both (preventing me from logging in and also preventing Facebook's password recovery scheme from e-mailing me a new password). Had the phisher been faster than me -- for example, if the phisher's systems were automated (and no doubt, some phisher's systems are or will be) -- I would have been locked out of my Facebook account and who knows what else.

I think I've headed a small disaster off at the pass. But who knows? Furthermore, the skin on my neck took on a slight rosy pigment as I poked around awardspace.com (apparently, a Web hosting company) to find out why such a phishing scam is so easily run off its domain. I also reached out to Google since, with the imposter URL, this is one e-mail that the Gmail antispam engine should have nuked with one eye closed.

Here's the image (and watch what you're clicking on!):

The Face Of A Facebook Phishing Scam


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links