AfterDawn: Tech news

Thousands will lose Internet on Monday; Make sure you don't

Written by James Delahunty @ 05 Jul 2012 7:12 User comments (13)

Thousands will lose Internet on Monday; Make sure you don't

FBI deadline may see thousands of Internet users unable to browse web.
These users have been affected by malicious software (dubbed DNSChanger, associated with TDL4 rootkits and a bootkit) that, among other nasty deeds, changes DNS settings on their PCs, Macs and maybe even wireless routers in order to present a spam-filled altered version of the Internet.

The FBI took down the rogue operation in November 2011 (Operation Ghost Click), but after it was found that hundreds of thousands of users were using the rogue DNS settings without knowledge, the decision was made to put clean DNS servers online using the same IP ranges as the malicious servers.

That bought infected users some time to detect and fix the problem. However, even with the support of giants like Google (which alerts some users in search results if their DNS settings appear altered), there are still reportedly hundreds of thousands of users worldwide who rely on the DNS servers - which are due to be disconnected on Monday, July 9.

What will happen if I'm affected on Monday?



If your DNS Settings are the notorious "Rove Digital" DNS settings, then your web browsers and other applications will lose the ability to carry out DNS lookups. Essentially, this means you will not be able to find the real location of websites when you type in domain names like www.afterdawn.com. You will get an error message like the one shown above.



This might not only affect a single infected computer. If your computer is connected to a router (including wireless), then the malware may have also altered the DNS settings of your router. If so, that means everything that connects through your wireless router (smartphone, Xbox 360, PS3, tablet, laptops etc.) will also be affected, even if they are totally clean of malware.

The only way to avoid this problem is to restore clean DNS settings. This might be more complicated than it sounds, because if your system is currently infected by the tedious malware, it may simply restore the bad DNS server settings once you try to change them. For this reason, you need to detect whether you are affected, then clean the infection and then change the DNS settings. To be clear, Wireless Routers are not infected by this malware, they simply have their DNS settings changed (if you use the default login/password combination, as most users do.)

So let's get started with detection.

Detect if DNS settings have been changed.



The easiest way to ensure that your DNS settings have not been changed to the Rove DNS servers is to try visiting a webpage that will determine if you are affected. We recommend that you visit http://www.dns-ok.us. You will either get a GREEN or RED result for DNS resolution. If you got a RED result, then you need to take action now.

Even if you received a GREEN result, it is possible that your ISP is redirecting DNS traffic, in which case you might still be infected with the malware (and your DNS settings might still be wrong) so take the following steps to manually confirm if you have been affected by this malware.



To manually check if you are affected by DNSChanger, we need to check what the DNS settings are on your PC or Mac, and check to see if they fall into any of the following ranges.
  • 85.255.112.0 - 85.255.127.255
  • 67.210.0.0 - 67.210.15.255
  • 93.188.160.0 - 93.188.167.255
  • 77.67.83.0 - 77.67.83.255
  • 213.109.64.0 - 213.109.79.255
  • 64.28.176.0 - 64.28.191.255

The above ipconfig read-out shows that the primary DNS server is 77.67.83.1, which falls into the range 77.67.83.0 - 77.67.83.255. This is a bad result and shows that this PC has been affected by the malware. So check your own computer manually following instructions below.

Check DNS on Windows XP
  • Click Start Menu.
  • Click Run.
  • Type "CMD" (without quotes).
  • Type "ipconfig /all" (without quotes) and press Enter.
  • Look through the results for Local Area Connection settings. Find "DNS Servers".
  • If the DNS server ranges match any of the malicious ranges shown above, then you are affected.

Check DNS on Windows Vista / 7
  • Click the Orb/Start Menu.
  • Type "CMD" into the search box (without quotes).
  • Run CMD.exe from the results.
  • Type >"ipconfig /all" (without quotes) and press Enter.
  • Look through the results for Local Area Connection settings. Find "DNS Servers".
  • If the DNS server ranges match any of the malicious ranges shown above, then you are affected.

Check DNS on Mac OS X
  • Click the Apple icon on the Desktop (top left).
  • Click System Preferences.
  • Open the Network preferences.
  • The DNS Server information will now be shown. If either IP fall within the malicious ranges shown above, then the system is affected.

It could be possible that you get a good result here, but still are warned by DNS-OK.us that you are affected. If that's the case, then your wireless router might just be the problem.

Is my Wireless Router affected?



Checking your Wireless Router is a little bit more complicated. You need to be able to see your wireless router settings, and this varies from model to model. Most routers will let you change settings through a web-interface, provided that you are connected to the router, know its IP address on the network and have the correct login information. For most users, this information will all be default unless you have decided to change it manually.

NOTE: If you have previously changed the login user name and password of your router, then it is highly unlikely that the DNS settings have been altered by any malware. The DNSChanger variant will only be able to change these settings if the routers username and password are the default settings.



To connect to the web interface of your router, you need the default information (or information provided by your ISP). If you have manuals or other information provided with the router then use that. Also, some ISPs will include this information (along with the Wi-Fi access key etc.) on a sticker on the underside of the router they give you. If you still cannot find the relevant information, then check this Default Password List, and use ipconfig /all again to determine the router IP (find the default gateway) and enter that into your browser.

So if your default gateway is 192.168.0.1, then type http://192.168.0.1 into your web browser and you should get a login prompt. This won't always be the case, but it will be for most consumer-level wireless routers.

Once you are able to check your Router settings, try to find the DNS settings (often time, you till find it under Network - WAN, but all routers vary). If your Router is set to retrieve all information via DHCP, then you are most likely OK, since the Router will retrieve the DNS IP addresses directly from your ISP. This won't always be the case though, and if you find DNS servers are manually set in the router and fall into the ranges shown above, then you will need to either change them to your ISP's settings (or set to DHCP / automatically retrieve settings) or to a public settings like Google DNS (8.8.8.8 and 8.8.4.4).

NOTE: Unfortunately, not all routers will be this easy to check, and you may need to contact your ISP if you are concerned about whether your router is affected. Otherwise, Google for information on your router model and find out how to change the settings. Be careful when resetting a router or restoring defaults, as you could end up with an unsecured network.

Removing the Malware infection


NOTE: This article only suggests measures that may free you from the malware infection responsible for the DNS server changes. AfterDawn accepts no responsibility for any negative consequences if you follow the advice below. Be smart and create a backup of personal files and anything else that might be important to you in the case that you might end up needing to re-install your operating system later to resolve the problem. Also, if you know a relative or friend that has more experience than you, bite the bullet and ask them to do this instead.



Options for Windows



Since the DNSCHanger malware is associated with the TDL4 (TDSS, Alureon) rootkit, which also affects boot options, TDSSKiller from Kaspersky can help with the removal process. Using TDSSKiller, you can detect and remove stubborn rootkit infections, as well as cure a bootkit. While this might not fix the problem for you right away, it will fix some really annoying things, such as the inability to use security software you may already have installed, or to download Windows and anti-virus updates.

Download TDSSKiller from:
http://support.kaspersky.com/faq/?qid=208283363

Running TDSSKiller is simple. Just run the utility and click Scan and let it do its thing. In Windows Vista / 7 you may need to right-click on the TDSSKiller executable and click Run as Administrator for it to work properly.

If the utility finds and removes nasty rootkits and bootkits from the system, you will still need to run other general anti-malware utilities to ensure the system is clean before switching the DNS settings back to automatic, or whatever you'd prefer.

Tools you can run after TDSSKiller that will help include...You should also make sure to install a security product, such as Avast Anti-Virus or AVG to help clean up any remnants of malware infection and to help prevent infection in the future.



DNSChanger Removal for Mac OS X

SecureMac offers a free DNSChanger Removal Tool for Mac OS X users. The tool will remove the OSX.RSPlug.A Trojan Horse and restore the DNS records (after a reboot).

Download the DNSChanger Removal Tool for Mac OS X from:
http://macscan.securemac.com/dnschanger-trojan-removal-tool-for-mac-os-x/

Restore safe DNS Settings



NOTE: Some security software you have previously run may already have restored your DNS settings.

Once you are confident your system is now free of the malware that causes the DNS changes, you can now manually change the DNS settings yourself.

Change DNS on Windows XP
  • Click Start.
  • Open Control Panel.
  • Switch to Classic View and open Network Connections.
  • Right-click on your active Local Area Connection, click Properties.
  • Select "Internet Protocol (TCP/IP)" and click Properties.
  • In the General tab, select Obtain DNS server address automatically OR manually enter your ISPs Preferred and Alternative DNS server IP addresses if you have them OR
  • If you do not have your ISP's DNS server addresses and automatically obtaining then is not working, then try 8.8.8.8 and 8.8.4.4 to use Google's public DNS servers instead.
  • Click OK and Apply settings.

Change DNS in Windows Vista
  • Click the Start / Orb menu button.
  • Click Control Panel.
  • Switch to Classic View and open Network and Sharing Center.
  • Click Manage Network Connections.
  • Right-click active Local Area Connection (or other active connection) and click Properties.
  • Select Internet Protocol (TCP/IPv4) and click Properties.
  • In the General Tab, select Obtain DNS server address automatically OR manually enter your ISPs Preferred and Alternative DNS server IP addresses if you have them OR
  • If you do not have your ISP's DNS server addresses and automatically obtaining then is not working, then try 8.8.8.8 and 8.8.4.4 to use Google's public DNS servers instead.
  • Click OK and Apply settings.

Change DNS in Windows 7
  • Click the Start / Orb menu button.
  • Click Control Panel.
  • Switch from Category View to Large Icons in the top-right, and then open Network and Sharing Center.
  • Click "Change Adapter Settings" on the left.
  • Right click on the Local Area Connection or Wireless Network Connection (depending on which is there, or which you are using), and click Properties.
  • Under the Networking tab, select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
  • In the General Tab, select Obtain DNS server address automatically OR manually enter your ISPs Preferred and Alternative DNS server IP addresses if you have them OR
  • If you do not have your ISP's DNS server addresses and automatically obtaining then is not working, then try 8.8.8.8 and 8.8.4.4 to use Google's public DNS servers instead.
  • Click OK and Apply settings.

Conclusion


Hopefully the information here will be helpful to some users. If you still have problems after trying out the information above, most ISPs should be more than willing to help if you try contacting a call center. Hopefully you will not turn out to be one of the unfortunate victims of this malware saga on Monday, July 9.

Previous Next  

13 user comments

15.7.2012 14:59

Well I won't be one of them so no problem for me.

25.7.2012 16:57

Good article posted, I passed this along to my friends to make sure they remember to check.

35.7.2012 17:48

I passed it on also but no one seemed interested.They were all to busy playing games on their facebook.I guess we'll see what happens if they can't get on next week.

45.7.2012 17:51

Originally posted by JST1946:
I passed it on also but no one seemed interested.They were all to busy playing games on their facebook.I guess we'll see what happens if they can't get on next week.
Wouldn't that be awful? They might actually have to work! eww! ;-)

55.7.2012 19:02

I did all the tests and recommendations in the article, and so far no problem for me. Good info!

66.7.2012 18:58

Originally posted by JST1946:
I passed it on also but no one seemed interested.They were all to busy playing games on their facebook.I guess we'll see what happens if they can't get on next week.
I did the same thing with friends family members. Most poopoo'd it, one told me to mind my own business, the rest were on Facebook and couldn't be bothered. Talk about sticking your head in the sand!!

78.7.2012 10:25

Originally posted by Semperfipal:
Originally posted by JST1946:
I passed it on also but no one seemed interested.They were all to busy playing games on their facebook.I guess we'll see what happens if they can't get on next week.
I did the same thing with friends family members. Most poopoo'd it, one told me to mind my own business, the rest were on Facebook and couldn't be bothered. Talk about sticking your head in the sand!!
Wow, the one who said mind your own business must be a right p.o.s.!!!!

88.7.2012 11:22

Originally posted by ST2006:
Originally posted by Semperfipal:
Originally posted by JST1946:
I passed it on also but no one seemed interested.They were all to busy playing games on their facebook.I guess we'll see what happens if they can't get on next week.
I did the same thing with friends family members. Most poopoo'd it, one told me to mind my own business, the rest were on Facebook and couldn't be bothered. Talk about sticking your head in the sand!!
Wow, the one who said mind your own business must be a right p.o.s.!!!!
Your right, it was my ex-wife! So much for open communication with former spouses. Ha!

98.7.2012 16:11

Great article! Too bad the majority will not accept the facts. Until the mainstream media picked this up, as JST1946 said, no one cared. Now here we are a few hours before midnight (just like December 31, 1999) and suddenly people are interested. I've been flooded with email, txt, phone calls (can you imagine?) asking "WHAT CAN I DO?

Sorry folks, I won't print my response but you get the picture.

108.7.2012 20:10

Good job covering this James Delahunty, kudos...

1110.7.2012 15:09

...and I think much like Y2K, people will wonder why they were so worried after it passes. This is not going to be some major Internet blackout. Statistically few people are going to be affected. The fix is easy. Go download Malwarebytes to a thumbdrive then install and run it. If your wireless router got infected, go do factory reset on it (honestly, if you didn't know enough to change the default password, I doubt you have a custom router config that a factory reset would wipe).

1210.7.2012 15:48

People were warned about a month or so in advance and then wait until the last minute and jump through their butts.I guess half of them can't read or follow intructions.
I sent this article to all my friends and relatives a couple of times and none of them responded until the day before.I'm not going to waste my time any more.

1311.7.2012 04:50

2pm monday was deadline in australia.i didnt waste my time checking to be honest.I have been reading the articles and new about this but i also knew it wouldnt affect me.

Comments have been disabled for this article.

News archive