Topics Map > University of Chicago > IT Services > Accounts, Identity, & Security > Security

DNSUnlocker Malware

This article explains the security precaution IT Security has taken to block all traffic to a set of malicious servers on the Internet associated with the malware DNSUnlocker. Infected machines will be unable to reach the controlling server, which will have the side effect of degrading service or making the the system unable to access the Internet. To restore service, you must remediate the malware.

The DNSUnlocker malware hijacks a computer's Domain Name Server configuration, redirecting traffic to a malicious external server, injecting ads into webpages visited, and adding an unauthorized root certificate to a computer's certificate store.

If your computer has a Domain Name Server (DNS) that starts with 82.163 (e.g. 82.163.143.157 or 82.163.142.159) or begins with 95.211.158. (e.g. 95.211.158.11 or 95.211.158.12) you are infected with a kind of malware known as DNSUnlocker. From a different system you can reference these online resources on how to see your DNS settings:

If you find yourself infected, your options include:

  1. Our recommendation in all cases of infection is to back up then reformat/reinstall or restore to a known good state. This is the only way you can be certain your computer is clean.
  2. As an alternative, since this malware does not try to hide itself, it may be possible to safely remove it:
    • Non-technical users should contact your local IT group for assistance. They can follow the instructions below or back up your data and reformat the computer.
    • Technical users could refer to this online walk-through guide that allows you to remove this malware yourself: DNSUnlocker removal instructions from BleepingComputer.

If you are unable to successfully remove the malware, IT Security recommends formatting the computer after backing up your data.




Keywords:trojan dns 82.163   Doc ID:61731
Owner:Jason E.Group:University of Chicago
Created:2016-03-08 13:44 CSTUpdated:2016-04-12 09:56 CST
Sites:University of Chicago, University of Chicago - Sandbox
Feedback:  2   0