MalwareBytes thinks avast! is malicious?

Avast Free Antivirus / Premium Security
1

Malwarebytes Keeps saying this error “Blocked a IP: 93.114.44.55”

This is the log:
"2013/11/14 13:48:45 +0200 JASCUALEX-PC (null) MESSAGE Executing scheduled update: Daily
2013/11/14 13:48:48 +0200 JASCUALEX-PC (null) MESSAGE Starting protection
2013/11/14 13:48:48 +0200 JASCUALEX-PC (null) MESSAGE Protection started successfully
2013/11/14 13:48:48 +0200 JASCUALEX-PC (null) MESSAGE Starting IP protection
2013/11/14 13:48:50 +0200 JASCUALEX-PC (null) MESSAGE IP Protection started successfully
2013/11/14 13:49:45 +0200 JASCUALEX-PC Jascu Alex MESSAGE Starting database refresh
2013/11/14 13:49:45 +0200 JASCUALEX-PC Jascu Alex MESSAGE Stopping IP protection
2013/11/14 13:49:45 +0200 JASCUALEX-PC Jascu Alex MESSAGE Scheduled update executed successfully: database updated from version v2013.11.13.04 to version v2013.11.14.04
2013/11/14 13:49:45 +0200 JASCUALEX-PC Jascu Alex MESSAGE IP Protection stopped successfully
2013/11/14 13:49:47 +0200 JASCUALEX-PC Jascu Alex MESSAGE Database refreshed successfully
2013/11/14 13:49:47 +0200 JASCUALEX-PC Jascu Alex MESSAGE Starting IP protection
2013/11/14 13:49:49 +0200 JASCUALEX-PC Jascu Alex MESSAGE IP Protection started successfully
2013/11/14 22:03:55 +0200 JASCUALEX-PC Jascu Alex IP-BLOCK 93.114.44.55 (Type: outgoing, Port: 53952, Process: avastsvc.exe)
2013/11/14 22:03:55 +0200 JASCUALEX-PC Jascu Alex IP-BLOCK 93.114.44.55 (Type: outgoing, Port: 53953, Process: avastsvc.exe)
2013/11/14 22:04:35 +0200 JASCUALEX-PC Jascu Alex IP-BLOCK 93.114.44.55 (Type: outgoing, Port: 53988, Process: avastsvc.exe)
2013/11/14 22:04:35 +0200 JASCUALEX-PC Jascu Alex IP-BLOCK 93.114.44.55 (Type: outgoing, Port: 53989, Process: avastsvc.exe)
2013/11/14 22:15:57 +0200 JASCUALEX-PC Jascu Alex IP-BLOCK 93.114.44.55 (Type: outgoing, Port: 54023, Process: avastsvc.exe)
2013/11/14 22:15:57 +0200 JASCUALEX-PC Jascu Alex IP-BLOCK 93.114.44.55 (Type: outgoing, Port: 54024, Process: avastsvc.exe)
2013/11/14 22:21:57 +0200 JASCUALEX-PC Jascu Alex IP-BLOCK 93.114.44.55 (Type: outgoing, Port: 54042, Process: avastsvc.exe)
2013/11/14 22:21:58 +0200 JASCUALEX-PC Jascu Alex IP-BLOCK 93.114.44.55 (Type: outgoing, Port: 54043, Process: avastsvc.exe)
2013/11/14 22:24:54 +0200 JASCUALEX-PC Jascu Alex IP-BLOCK 93.114.44.55 (Type: outgoing, Port: 54051, Process: avastsvc.exe)
2013/11/14 22:24:54 +0200 JASCUALEX-PC Jascu Alex IP-BLOCK 93.114.44.55 (Type: outgoing, Port: 54052, Process: avastsvc.exe)
2013/11/14 22:34:48 +0200 JASCUALEX-PC Jascu Alex IP-BLOCK 93.114.44.55 (Type: outgoing, Port: 54073, Process: avastsvc.exe)
2013/11/14 22:34:48 +0200 JASCUALEX-PC Jascu Alex IP-BLOCK 93.114.44.55 (Type: outgoing, Port: 54074, Process: avastsvc.exe)
2013/11/14 22:35:13 +0200 JASCUALEX-PC Jascu Alex MESSAGE Stopping IP protection
2013/11/14 22:35:13 +0200 JASCUALEX-PC Jascu Alex MESSAGE IP Protection stopped successfully
2013/11/14 22:35:13 +0200 JASCUALEX-PC Jascu Alex MESSAGE Starting IP protection
2013/11/14 22:35:15 +0200 JASCUALEX-PC Jascu Alex MESSAGE IP Protection started successfully
"

Help?

2
2013/11/14 22:03:55 +0200 JASCUALEX-PC Jascu Alex IP-BLOCK 93.114.44.55 (Type: outgoing, Port: 53952, [b]Process: avastsvc.exe[/b])
this has been posted many times before..... all in/out requests goes true avast webshield.... so MBAM see it as coming from avast....it is not

also read this about what MBAM is blocking

Oh, the Sites You Will Never See http://blog.malwarebytes.org/development/2013/05/oh-the-sites-you-will-never-see/

3

MBAM explained it to me this way, “it isn’t really blocking avast”.
I’ve noticed that this happens whenever avast send out a vps update.
Just make the exclusion in MBAM and you will be fine. :slight_smile:

4

Until it is confirmed with Malwarebytes I wouldn’t be excluding anything, it’s not an avast IP that was detected.

Most times when I receive these blocked messages it is due to some image or link on a page that is trying to call home so it’s best off blocked imo.

5

The IP address belongs to voxility(dot)net and appears to be risky.
See http://zulu.zscaler.com/submission/show/fb27961f99fd67c831509fd5badcc7f2-1384540616
and https://asafaweb.com/Scan?Url=voxility.net

Clickjacking explained here.

I have made mutual exclusions in both avast and MBAM. Making the
exclusions does not diminish the efficacy of either.

6

Upon further research I found http://whois.domaintools.com/voxility.net

7

The exclusions I was talking about was not concerning exclusions between avast and MBAM, I was referencing to you having mentioned " Just make the exclusion in MBAM and you will be fine " when the MBAM popup warning was not avast related which would have resulted in the OP excluding the suspicious IP.

8

Yes, as for mutual exclusions, I agree it certainly doesn’t hurt.
I personally seem to have been fortunate as I have not experienced conflict between Avast and MBam on my Win8.1.
On my XP, I did mutually exclude Avast and MBam as a precaution but don’t recall any conflict on the old system either.

9

This may help:
Avast and Malwarebytes mutual Exclusions