Author Topic: URL:Mal error  (Read 2244 times)

0 Members and 1 Guest are viewing this topic.

Offline vaibhav.p

  • Newbie
  • *
  • Posts: 2
URL:Mal error
« on: May 05, 2015, 12:54:50 PM »
Hi there,

my company owns srv.tyroodr.com domain and users have been complaining of getting an infection blocked popup. We have done extensive tests and haven't found any malicious code / warnings at our end. Can you help us figure out what could be causing this issue? We also use Cloudflare for serving our content and they too have confirmed that they didn't see any issues with our content.


URL to test:

hxtp://srv.tyroodr.com/www/delivery/ckt.php?bannerid=17643048&affid=297&subid1=0a3049fb-c3b1-483c-871c-40b6caf4dccd&subid2=16374


Error seen:
Infection detected!
hxtp://srv.tyroodr.com/www/delivery/ckt.php?bannerid=17643048&affid=297&subid1=0a3049fb-c3b1-483c-871c-40b6caf4dccd&subid2=16374

The requested URL contains malicious code that can damage your computer. If you want to access the URL anyway, turn off the Avast web shield and try it again.

Infection type: URL:Mal

« Last Edit: May 05, 2015, 03:11:17 PM by Milos »

Offline denics

  • Avast team
  • Full Member
  • *
  • Posts: 168
    • avast!
Re: URL:Mal error
« Reply #1 on: May 05, 2015, 03:59:03 PM »
Hi,

it was a false positive and it will be fixed in the next virus database update. We're sorry for the inconvenience.

Best regards
Denis Konopisk√Ĺ - avast! VirusLab | Android & Windows Malware | VPS Operations | Whitelisting

Offline vaibhav.p

  • Newbie
  • *
  • Posts: 2
Re: URL:Mal error
« Reply #2 on: May 06, 2015, 03:45:17 AM »
Thank you. Looking forward to the next update :)

Hi,

it was a false positive and it will be fixed in the next virus database update. We're sorry for the inconvenience.

Best regards

Offline Jonathan158

  • Newbie
  • *
  • Posts: 1
Re: URL:Mal error
« Reply #3 on: May 26, 2015, 01:52:58 PM »
Hi,

Some customers have reported me that they use Avast, and when they login to www.amgpiscinas.com were blocked by Avast

I have attached a file with the error.

Is the same error?

Regards,