Dear valued Bank of America® member,
Due to a recent high number of fraudulent transactions, we haveissued the following security requirements.
It has come to our attention that 98% of all fraudulenttransactions are caused by fraudsters using stolen account information to purchaseor sell non existant items. Thus we require our members to enroll in ourSiteKey security upgrade, as part of our continuing commitment to protectyour account and to reduce the instance of fraud on our website. Afteryou submit the requested information, we will create a unique algorithmbased on your personal computer, allowing us to recognize you in anyfuture online banking sessions and thus immediately spotting anyunauthorized access. By passing back and forth secret information that only youand Bank Of America know, you can feel even more secure withyour online banking experience. We recognize you and you recognize us. If youcould please take 5-10 minutes out of your online experience and enrollin the SiteKey security upgrade, you will not run into any future problemswith the Bank Of America® online banking service. However,failure to meet our security requirements will result in your accountsuspension.
We are requesting this information to verify and protect youridentity. Federal regulations require all financial institutions to obtain,verify, and record identification from all persons opening new accounts orobtaining ongoing payment services. This is in order to prevent the use ofthe U.S. banking system in terrorist and other illegal activity. For thesereasons, Bank Of America® will utilize services provided by variouscredit reporting agencies to verify the information you submit to us.
Once you have enrolled in our SiteKey security upgrade your pendingBank Of America account transactions will not be interrupted andwill continue as normal.
Please enroll in our SiteKey security upgrade by clicking here.
Thank you for your time,
Regards,
M.Sam Harvey
Bank Of America® Security Department.
Lets have a look at the email header:
| Return-Path: | <me@laa.com> |
| Delivered-To: | me@mprdmailbe.nwk.myway.com |
| Received: | (qmail 8241 invoked from network); 10 Feb 2008 11:55:59 -0000 |
| Received: | from unknown (HELO mprdmx5.nwk.myway.com) ([10.50.31.18]) (envelope-sender <me@laa.com>) |
| by 0 (qmail-ldap-1.03) with SMTP | |
| for <meg215@mprdmailbe.nwk.myway.com>; 10 Feb 2008 11:55:59 -0000 | |
| Return-Path: | <me@laa.com> |
| Received: | from laa.com (pool-71-173-92-110.ptldme.east.verizon.net [71.173.92.110]) |
| by mprdmx5.nwk.myway.com (Postfix) with SMTP id 571294BDBC; | |
| Sun, 10 Feb 2008 06:55:51 -0500 (EST) | |
| Message-ID: | <60DA82F6.949BFB0B@laa.com> |
| Date: | Sun, 10 Feb 2008 13:32:41 +0100 |
| From: | "Bank Of America" <me@laa.com> [ Add to Address Book | Block Address | Report as Spam ] |
| User-Agent: | Opera/7.11 (Windows NT 5.0; U) |
| MIME-Version: | 1.0 |
| To: | "me" <me@myway.com> |
| Subject: | Account Security Measures! |
| Content-Type: | text/html; |
| charset="iso-8859-1" | |
| Content-Transfer-Encoding: | 7bit |
| X-FII-Tracking: | 0.131430 |
I am not the greatest at deciphering these headers, but they clearly do not have anything to do with BofA, and BofA would not send an email like this anyway.
