|
Date Reported: 16th December 2009 |
Risk Level: MEDIUM |
|
|
|
|
|
Email Subject: |
[GFI--DNSBL] - possible fraudulent transaction occurred with your VISA card - Dynamic IP detected |
|
Apparent Sender: |
VISA |
|
Return Address: |
message_K3IPUJ918WXZ7id@mail.visa.com |
|
Email Format: |
HTML |
|
URL of Web Content: |
http://sessionidAKCB0ZO57.visa.com.upemiiti.be/car ds/myvisa/transactions.php?ref5245796468817306494 2765384724030709137&email=hewlettt661@sciencef riday.com |
|
Anchor text of URLs: |
1) http://sessionidAKCB0ZO57.visa.com/cards/myvi sa/transactions.php?ref524579646881730649427 65384724030709137&email=martinb@bmcatalys ts.co.uk |
|
Location: |
Location not available |
|
Scam number: |
6538-87618-301236 |
|
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.
|
|
|
|
|
|
|
|
|
Dear VISA card holder,
A recent review of your transaction history determined that your card was used at an ATM located in Georgia, but for security reasons the requested transaction was refused.Please carefully review electronic report for your VISA card at:
HTTP://SESSIONIDAKCB0ZO57.VISA.COM/CARDS/MYV ISA/TRANSACTIONS.PHP?REF52457964688173064942 765384724030709137font-family:"Arial","sans-s erif"'>ID: 3AT5HE834O5PR2JBQ7YYY9QF1NDN163B24MS
This message and any ...
|
|
Click for full size image |
|
Website: |
|
|
|
|
Website was not online when we checked. It returned the error 404 |