|
Date Reported: 16th December 2009  |
Risk Level: MEDIUM |
|
| |
 |
 |
| |
Email Subject: |
[GFI--RAZER] - VISA 4XXX XXXX XXXX XXXX: possible fraudulent transaction ID 31769178813820 - Message was |
|
Apparent Sender: |
VISA |
|
Return Address: |
alerts@mail.visa.com |
|
| Email Format: |
HTML |
| |
URL of Web Content: |
http://reports.visa.com.ipetiiti.be/cards/myvisa/t
ransactions.php?ref“046895676305328798607414413184
356715&emailúctorizationv60@rautenschlein.com
|
|
Anchor text of URLs: |
1)
http://reports.visa.com/cards/myvisa/transact
ions.php?ref“04689567630532879860741441318435
6715&email=markb@bmcatalysts.co.uk |
|
Location: |
Location not available |
| |
Scam number: |
6540-87620-301238 |
| |
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.
|
| |
|
|
|
 |
| |
|
| |
found to be spam: (100%) IP is in RBL
Dear VISA card holder,
A recent review of your transaction history
determined that your card was used at an ATM
located in Ecuador, but for
security reasons the requested transaction
was refused.Please carefully review
electronic report for your VISA card at:
HTTP://REPORTS.VISA.COM/CARDS/MYVISA/TRANSAC
TIONS.PHP?REF“0468956763053287986074144131843
56715font-family:"Arial","sans-serif"'>Ref:
9C7J9DV233M2N5R63380W59R4620Q4803VM1I...
|
|
Click for full size image |
| |
| Website: |
|
|
| |
|
| Website was not online when we checked. It returned the error 404 |
