Unchecky hosts file sometimes causes 0.0.0.0 to be resolved to the first blocked host.

With a default Unchecky install, ESET Smart Security shows programs that are listening on 0.0.0.0 (all interfaces) resolved to the first blocked host, (In my case, tracking.opencandy.com.s3.amazonaws.com ).  Netstat does not appear to experience the same symptom. 

As you can imagine, seeing this host repeatedly in my list of active network connections, without immediately realizing why, was alarming.

I fixed it by adding the following line to the top of my hosts file (0.0.0.0 repeated twice):

0.0.0.0 0.0.0.0

This prevented ESET from resolving 0.0.0.0 to tracking.opencandy.com.s3.amazonaws.com and has not caused any noticeable side effects.