|
Date Reported: 16th December 2009  |
Risk Level: MEDIUM |
|
| |
 |
 |
| |
Email Subject: |
[GFI--RAZER] - possible fraudulent transaction occurred - Message was found to be : (100%) Contains |
|
Apparent Sender: |
VISA |
|
Return Address: |
message_DE6FQ7WKS8P48Xid@mail.visa.com |
|
| Email Format: |
HTML |
| |
URL of Web Content: |
http://alerts.visa.com.upetkiti.be/cards/myvisa/tr
ansactions.php?ref€3128433763211502230210877182346
816&email=pummelinge90@rocexhibitions.com
|
|
Anchor text of URLs: |
1)
http://alerts.visa.com/cards/myvisa/transacti
ons.php?ref€312843376321150223021087718234681
6&email=markb@bmcatalysts.co.uk |
|
Location: |
Location not available |
| |
Scam number: |
6539-87619-301237 |
| |
Comments: |
- Email asks you to confirm/update/verify your account data at VISA by visiting the given link. You will be taken to a spoof website where your details will be captured for the phishers.
- VISA never send their users emails requesting personal details in this way.
- The anchor text appears as a legitimate URL, but don't be fooled - clicking on it will take you to a phishing site!
- 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.
|
| |
|
|
|
 |
| |
|
| |
spammy domain
Dear VISA card holder,
A recent review of your transaction history
determined that your card was used at an ATM
located in Uruguay, but for
security reasons the requested transaction
was refused.Please carefully review
electronic report for your VISA card at:
HTTP://ALERTS.VISA.COM/CARDS/MYVISA/TRANSACT
IONS.PHP?REF€31284337632115022302108771823468
16font-family:"Arial","sans-serif"'>Message
ID:
2RQDMA2ORPPNBF0ZJ537YOBA594G1GVW54U4BSERDCWU7
ETC55FVC5E7I...
|
|
Click for full size image |
| |
| Website: |
|
|
| |
|
| Website was not online when we checked. It returned the error 404 |
