Pages

Wednesday, July 9

.mac phishing? Say it ain't so


Check this guy out!  Phishing attempt specifically targeted at mac.com users.  Be aware for this one!  

 Subscribe in a reader

14 comments:

Todders said...

I got hit by the about ten minutes ago myself, before seeing your lost linked form MacSurfer. It was reasonably convincing; for a moment I thought it might have been some glitch with the MobileMe changeover.

Joel Esler said...

I've contacted Apple Security, they notified their .mac team for remediation!

Quick response!

I'm Randy Harris.... said...

Seems like phishermen would spend more time on editing their copy. I can't imagine Apple (who does employ copyreaders) would allow an email to go out with a comma where a period should be, or with garbled syntax such as "correct july [whoops, should be upper case] 2008.

Todders said...

I got hit by the about ten minutes ago myself, before seeing your lost linked form MacSurfer. It was reasonably convincing; for a moment I thought it might have been some glitch with the MobileMe changeover.

Todders said...

I got hit by the about ten minutes ago myself, before seeing your lost linked form MacSurfer. It was reasonably convincing; for a moment I thought it might have been some glitch with the MobileMe changeover.

Joel Esler said...

I've contacted Apple Security, they notified their .mac team for remediation!Quick response!

Joel Esler said...

I've contacted Apple Security, they notified their .mac team for remediation!Quick response!

I'm Randy Harris.... said...

Seems like phishermen would spend more time on editing their copy. I can't imagine Apple (who does employ copyreaders) would allow an email to go out with a comma where a period should be, or with garbled syntax such as "correct july [whoops, should be upper case] 2008.

I'm Randy Harris.... said...

Seems like phishermen would spend more time on editing their copy. I can't imagine Apple (who does employ copyreaders) would allow an email to go out with a comma where a period should be, or with garbled syntax such as "correct july [whoops, should be upper case] 2008.

Jane said...

@I'm Randy Harris:I actually got the same email, but it was worded slightly differently:We were unable to process your most recent payment. Did you recently change your bank, phone number or credit card?To ensure that your service is not interrupted, please update your billing information today by clicking here , After a few clicks, just verify the information you entered is correct.

Jane said...

@I'm Randy Harris:I actually got the same email, but it was worded slightly differently:We were unable to process your most recent payment. Did you recently change your bank, phone number or credit card?To ensure that your service is not interrupted, please update your billing information today by clicking here , After a few clicks, just verify the information you entered is correct.

Joel Esler said...

I've probably received 10 copies of this. I've sent them all to Apple and the MobileMe team is working on it.

Joel Esler said...

I've probably received 10 copies of this. I've sent them all to Apple and the MobileMe team is working on it.

Joel Esler said...

I've probably received 10 copies of this. I've sent them all to Apple and the MobileMe team is working on it.