false positive virus detection !

Hello

we are owners of http://zenitbet.com
and found FALSE positive virus detection on our site on computers, with avast installed
we manually check source code of all scripts and find nothing suspicious

also we check site with some online antivirus tools, like:

http://www.google.com/safebrowsing/diagnostic?site=zenitbet.com
http://www.unmaskparasites.com/security-report/
http://www.avg.com.au/resources/web-page-scanner/
http://safeweb.norton.com/report/show?url=zenitbet.com

viruses not detected.

also we check site with Kasperskiy antivirus 2012 whith latest v. bases -nothing found

please remove our site from virus databaes as soon as possible(we loose clients!)
or
tell us which script are infected.

with best regards zenitbet.com support team.

Report 2011-09-24 09:00:38 (GMT 1)
Website zenitbet.com
Domain Hash 830ff22d00b4f07c9f73fc9aac312d0c
IP Address 193.161.86.133 [SCAN]
IP Hostname 133.86.161.193.host-telecom.com
IP Country NO (Norway)
AS Number N/A
AS Name N/A
Detections 0 / 23 (0 %)
Status CLEAN

Report 2011-09-24 10:03:05 (GMT 1)
IP Address 193.161.86.133
IP Hostname 133.86.161.193.host-telecom.com
IP Country NO
AS Number N/A
AS Name N/A
Detections 0 / 26 (0 %)
Status CLEAN

Report a possible FP here: http://www.avast.com/contact-form.php?loadStyles

“Strange” that, according to the OP, Avast identifies the site with malware, but the index.html, according to Virustotal, is not.

Of course the problem could be elsewhere in the site, but usually users get to the index page first (and there, they shouldn’t see any problem).

Having said that, checking the index.html in VT is not the same as actually surfing the site (which may very well load some additional code other than index.html), so it is indeed possible.

Anyway, Asyn already gave the most effective method to report it :).

@ neomag
It is blocked by the network shield, but the home page causes no alert by the web shield. I don’t know if you have recently had a malware problem on the site which has now been cleaned up.

Follow up the reporting suggestion by Asyn, above.
When reporting a False Positive on a web site, then you get another input field open, enter the web URL for the site. Stating in the Message box, that you wish a ‘Network Shield’ review, etc. A link to this topic won’t hurt as it contains useful information too.

Hello users avast antivirus. I have the same problem with access to the site, I wrote a letter about this issue, as suggested @davidr. But do not get an answer within 10 hours.

In this case the entire domain is blocked completely, when you click on details, see nothing wrong, it is written:
Infection Details
URL: http://www.zenitbet.com/
Process: file: / / C: \ Program Files (x86) \ Mozilla Firefox \ firefox.exe
Infection: al

What kind of infection - is unclear. Antivirus NOD, KAV, AVG does not see the domain are no viruses.

Most interesting is that if the go to this domain via ip address, then either AVAST sees no threat.

Then what happens? AVAST blocking a site based on some lists or antivirus should work on code analysis? If AVAST analyzes the code, why does he allow the use of this site by its ip address?

Dear forum users, moderators tell me what to do in this situation, how to get this site from the blacklist?

See Reply #1.

Hi Asyn,

Probably the FP is alerted via md5.js Checking: -http://zenitbet.com/md5.js
File size: 8573 bytes
File MD5: 4625b010a0be04e04aa130cbc9fa05f2
-zenitbet.com/md5.js benign
[nothing detected] -zenitbet.com/md5.js
status: (referer=-www.google.com/trends/hottrends)saved 8573 bytes 3e4801af78b490451101689f690ab7367ca9f375
info: [decodingLevel=0] found JavaScript
file: 3e4801af78b490451101689f690ab7367ca9f375: 8573 bytes

polonus

Hi D,
probably, but the virus lab guys have the final word on this. :wink:
Have a nice weekend,
asyn

As I understand Avast has no a feedback on the weekend?

It depends. :wink:
The VL is also active on weekends.

We’ll wait for an answer on monday when AVASTsup rest in weekend.

Thanks to active participants of Forum for help in solving the problem.

You’re welcome…!

This was already fixed internally. Sorry for any inconvenience.