Author Topic: False Malicious URL  (Read 2111 times)

0 Members and 1 Guest are viewing this topic.

reddleman2

  • Guest
False Malicious URL
« on: October 17, 2012, 08:39:04 PM »
Since this morning (17th October) Avast has indicated my site as being a malicious url. I have scanned my site (with Avast software) but that didn't come up with anything. I also checked with some analysis sites, but they didn't find anything either. I run a drupal installment with the latest security updates and I haven't installed any modules this week. So the only conclusion I can come with is a false positive.

Is there anything else I can do, or should I hope Avast will resolve the issue?

site: http://www.chronos-larp.nl
ip:  95.170.72.116 

Offline Pondus

  • Probably Bot
  • ****
  • Posts: 37536
  • Not a avast user
Re: False Malicious URL
« Reply #1 on: October 17, 2012, 08:53:50 PM »
you can report False Positive here   http://www.avast.com/contact-form.php

also include a link to this topic...

Offline polonus

  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 33905
  • malware fighter
Re: False Malicious URL
« Reply #2 on: October 17, 2012, 09:34:59 PM »
Hi Pondus,

The IP might have been blocked by avast, because of being a phish
Flagged: htxp://www.muziektheater-teer.nl/wp-content/uploads/2012/santander.htm
acording to Phishwatch 2012-04-26 also for domain -> light1to7 dot nl
AS report Blacklisted URLs: 55

Hosts...
...malicious URLs? Yes 
...badware? Yes 
...botnet C&C servers? No 
...exploit servers? Yes 
...Zeus botnet servers? No 
...Current Events? Yes 
...phishing servers? No 

polonus
Cybersecurity is more of an attitude than anything else. Avast Evangelists.

Use NoScript, a limited user account and a virtual machine and be safe(r)!

reddleman2

  • Guest
Re: False Malicious URL
« Reply #3 on: October 17, 2012, 10:27:58 PM »
I got a (very fast  :)) reply which stated there was a malicious website on the same server and they block the whole server. They unblocked my site, but I understand this is just a temporal solution. It's now between me and my service provider to solve the issue.

Thanks for the replies, much appreciated!