|
Date Reported: 27th April 2010  |
Risk Level: MEDIUM |
|
| |
 |
 |
| |
Email Subject: |
Update Your BT Email Account Details Now ! |
|
Apparent Sender: |
BT Yahoo Alert ! |
|
Return Address: |
accounts@btinternet.com |
|
| Email Format: |
HTML |
| |
URL of Web Content: |
http://pufek77.com/wp-%0d%0a%0d%0acontent/themes/d
efault/bt/index.html
|
|
Anchor text of URLs: |
1)
From: BT Yahoo Alert
!
[mailto:accounts@btinternet.com]
Sent: 27
April 2010 12:33
To: -censored by
MillerSmiles-
Subject: Update Your BT Email
Account Details Now !
Welcome to
BT Yahoo
We are using the medium to bring
it to your notice that BT Yahoo is
current
upgrading their security server and
we need you to provide you
BT(btinternet
& btopenworld) account
details, so we can proceed your email
upgrade.
Follow the link below to
proceed.
From : BT Yahoo Account Management |
|
Location: |
Location not available |
| |
Scam number: |
9580-126936-363415 |
| |
Comments: |
- Email asks you to confirm/update/verify your account data at BT Yahoo Alert ! by visiting the given link. You will be taken to a spoof website where your details will be captured for the phishers.
- BT Yahoo Alert ! never send their users emails requesting personal details in this way.
- The spoof website this email links to was not online at time of this report, but variations of the scam which link to working websites are bound to exist, so be wary! The website may have been taken down or disabled by the hosts, but quite often these websites are hosted on the personal computer of the phishers, so may only be online at certain times.
|
| |
|
|
|
 |
| |
|
| |
WELCOME TO BT YAHOO
We are using the medium to bring it to your
notice that BT Yahoo is current upgrading
their security server and we need
you to provide you BT(btinternet &
btopenworld) account details, so we can
proceed your email upgrade. Follow the link
below to proceed.
From : BT Yahoo Account Management
Thank you for using BT Yahoo.
...
|
|
Click for full size image |
| |
| Website: |
|
|
| |
|
| Website was not online when we checked. It returned the error 500 |
