|
|
phishingWhat to do if you get hit by the Facebook brunga.at virus attackMost of my hits lately have been people searching for information on bunga.at or another variant, like kirgo.at, nutpic.at, or 151.im. I've put together bits and pieces of information on the continuing Facebook phishing attack, but here's a quick guide on what to do if you've already fallen for it:
Facebook itself had a few anti-phishing recommendations:
Further Reading:
Facebook virus attacks continues: Check kirgo.at, nutpic.at, and brunga.at continue to lure unwary
Looks like claims to have cleaned up the the Facebook 151.im worm were a bit premature. I've gotten three more offers to check scam sites in the past few hours, including to Kirgo.at, nutpic.at, and brunga.at. It looks like the phishers have changed from the Isle of Man's .im domain to Austria's .at. I'd still pick the former this time of year. Most of what I wrote about the Facebook virus previously still applies, although it looks like the bad guys' servers are having trouble handling all the images, which will hopefully slow down the amount of people falling for the trick. One way to make sure that it's the real Facebook site you're logging in to? Simply put in a made up e-mail and password in the login page. The phishing sites have been putting out a "502 Bad Gateway" error, while the real Facebook would ask you to try again. Note that this is not a 100% fool proof method (check the address bar!), but few phishers, particularly for a scheme like this, are likely to go through the trouble of a complicated input verification scheme. Further Reading:
Facebook says "Check 121.im"; Common sense says don'tSince I've already gotten two of the spam Facebook messages today, I figure other people probably are, too. What sets this phishing attack from others? For one, no obvious misspellings:
Pretty much identical to a regular Facebook message:
Still, it's a good reminder that avoiding phishing traps is easy: Always, always, always look at the address bar when you enter your password and username for any website, whether it's a bank, social networking site, or e-mail. Even if only a trivial account is compromised, many users use the same passwords across all their logins, meaning big trouble even if it's the most clueless script kiddie who gets your data. Update: Facebook has acknowledged the virus, and is taking steps to thwart its effects, the L.A. Times reports. "This is a phishing attack. We’re well aware of it and are already blocking links to these new phishing sites from being shared on Facebook," Facebook e-mailed the LA Times. "We’re also cleaning up phony messages and Wall posts and resetting the passwords of affected users. We think this is related to the fbaction.net/fbstarter.com campaign of a couple weeks ago. " Facebook has also put a better anti-phishing blog post than mine on preventing attacks, though it would be nice (if expensive to them) to make SSL the default connection. Update 2: Removed some Real Life (TM) first names I'd accidentally left in, to protect the innocent and guilty. Further Reading:
|