Twitter Phisher Now Targeting Digg?

by Lee on January 7, 2009

in Social Network Security

It would appear that Twitter is not the only social networking site being targeted by phishers at this time.

They are now after another of the big guns – Digg.

digg

Copycat

A clone of Digg, which looks identical to the genuine site, has been released.

Those behind it seem to be dropping the URL wherever they can and, in particular, on other social networking sites such as Twitter.

By using a URL shortening service, such as Tiny URL, they are able to mask the real website address (http://567gu.com is the site to avoid).

Of course, you shouldn’t visit that fake website and you most certainly shouldn’t attempt to sign in there.

If you do, you’ll lose your Digg account and will be allowing someone complete control over your future Diggs, friends, shouts, etc.

The Shanghai Connection

Interestingly, a Whois lookup on the registrant of the offending domain reveals that the site is, apparently, located in Shanghai, China.

Why is that interesting?

Because the fake Twitter domain I wrote about a couple of days ago was also coming out of Shanghai.

An unlikely coincidence or could it be the same person behind both?

Related Posts

  • 50 More InfoSec Nuts To Follow On Twitter
  • 4 Ways To Spot A Twitter Spammer
  • Security Alert : Phishing Attempt On Twitter
  • Why Did I Suddenly Lose Loads Of Twitter Followers?
  • Twitter – Scam, Spam & Security
  • Twitter Limits Malware Links
  • Confessions Of A Twitter Spammer
  • Follow Me, Unfollow You – Gaming Twitter
  • Hannah Montana’s Miley Cyrus Killed In Car Crash?
  • Koobface Virus Migrates From Facebook To Twitter
  • { 2 comments… read them below or add one }

    1 Mark January 9, 2009 at 11:10 am

    It looks like it is the same person behind both though I though the internet access in China was limited?

    Reply

    2 Lee January 10, 2009 at 12:48 am

    That’s my belief too Mark, though I don’t think the government block or censor everything.

    Reply

    Leave a Comment

    Previous post:

    Next post: