Does anyone know the history of bfi0.com vis-à-vis suspected phishing?  I
googled them and saw that a lot of people are unsure.  Here are partial
headers (up to my gateway - my info hopefully changed/removed) of a recent
e-mail I received purporting to be from MetLife - all the links in the
e-mail go to bfi0.com (BigFoot Interactive) instead of MetLife.  They appear
to be a third party who does marketing/remailing for other companies: Target
& Capital One for instance.  However, I'd like a second opinion.

I e-mailed MetLife several hours ago and haven't heard anything back.

Thanks,
Dave
--
Dave Cohoe, CISSP, RHCT, MCP
http://dave.cohoe.googlepages.com
"The future is already here. It's just not very evenly distributed." -
William Gibson

---------- Forwarded message ----------

Microsoft Mail Internet Headers Version 2.0
Received: from bigfootinteractive.com (arm-ei57.bigfootinteractive.com [
216.33.63.57 ])
       by smtp-gateway-4a.company.us (8.13.1/8.13.1) with SMTP id
l1FD5tcI014985
       for <[EMAIL PROTECTED]>; Thu, 15 Feb 2007 05:05:56 -0800
Reply-To: MetLife Dental Claims
<[EMAIL PROTECTED]>
Bounces_to: [EMAIL PROTECTED]
Message-Id: <[EMAIL PROTECTED]

X-BFI: W1TH056132218D866401F309AE5230
Date: Thu, 15 Feb 2007 08:05:55 EST
From: MetLife Dental Claims <[EMAIL PROTECTED]>
Subject: Your recent dental claim is ready for your review
To: [EMAIL PROTECTED]
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="ABCD-W1TH056132218D866401F309AE5230-EFGH"
Sender: [EMAIL PROTECTED]
X-OriginalArrivalTime: 15 Feb 2007 13:06:02.0571 (UTC)
FILETIME=[0B5BF9B0:01C75102]

--ABCD-W1TH056132218D866401F309AE5230-EFGH
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable

--ABCD-W1TH056132218D866401F309AE5230-EFGH
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: quoted-printable


--ABCD-W1TH056132218D866401F309AE5230-EFGH--
_______________________________________________
phishing mailing list
[email protected]
http://www.whitestar.linuxbox.org/mailman/listinfo/phishing

Reply via email to