Contact them via virus AT avast dot com and point out the problem and give a link to the discussion here.
This is an interesting report from Asafaweb for the top-level-domain uri:
Custom errors: FailRequested URL:
http://kunz.corrupt.ch/< | Response URL:
http://kunz.corrupt.ch/< | Page title: Runtime Error | HTTP status code: 400 (Bad request) | Response size: 3,420 bytes | Duration: 113 ms
Overview
Custom errors are used to ensure that internal error messages are not exposed to end users. Instead, a custom error message should be returned which provides a friendlier user experience and keeps potentially sensitive internal implementation information away from public view.
Result
It looks like custom errors are not correctly configured as the requested URL contains the heading "Server Error in".
Custom errors are easy to enable, just configure the web.config to ensure the mode is either "On" or "RemoteOnly" and ensure there is a valid "defaultRedirect" defined for a custom error page as follows:
<customErrors mode="RemoteOnly" defaultRedirect="~/Error" />
Then there is this:
Excessive headers: Warning
Requested URL:
http://kunz.corrupt.ch/ | Response URL:
http://kunz.corrupt.ch/ | Page title: TAL- Togu Audio Line: Home | HTTP status code: 200 (OK) | Response size: 13,498 bytes | Duration: 760 ms
Overview
By default, excessive information about the server and frameworks used by an ASP.NET application are returned in the response headers. These headers can be used to help identify security flaws which may exist as a result of the choice of technology exposed in these headers.
Result
The address you entered is unnecessarily exposing the following response headers which divulge its choice of web platform:
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
X-AspNetMvc-Version: 3.0
Configuring the application to not return unnecessary headers keeps this information silent and makes it significantly more difficult to identify the underlying frameworks.
Shhh… don’t let your response headers talk too loudly
And Clickjacking: Warning
Requested URL:
http://kunz.corrupt.ch/ | Response URL:
http://kunz.corrupt.ch/ | Page title: TAL- Togu Audio Line: Home | HTTP status code: 200 (OK) | Response size: 13,498 bytes | Duration: 760 ms
Overview
Websites are at risk of a clickjacking attack when they allow content to be embedded within a frame. An attacker may use this risk to invisibly load the target website into their own site and trick users into clicking on links which they never intended to. An "X-Frame-Options" header should be sent by the server to either deny framing of content, only allow it from the same origin or allow it from a trusted URIs.
Result
It doesn't look like an X-Frame-Options header was returned from the server which means that this website could be at risk of a clickjacking attack. Add a header to explicitly describe the acceptable framing practices (if any) for this site (info from recent Asafaweb scan)
For the download I get a 502 Bad Gateway -
For the Anubis report on one of the downloads see:
http://anubis.iseclab.org/?action=result&task_id=12ba3e987e5c1d894e1a01630acbceabfGonna comment more on that later, the main conclusion I give further down!*
Response Header:
HTTP Response Header
Name Value Delim
Status: HTTP/1.1 200 OK
Content-Type: application/x-zip-compressed
Last-Modified: Wed, 25 Sep 2013 08:11:12 GMT
Accept-Ranges: bytes
ETag: "4c2f66ccc6b9ce1:0"
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Date: Thu, 26 Sep 2013 09:07:29 GMT
Connection: close
Content-Length: 17075783
From that Anubis report
the most important conslusion is:
Highly suspicious network connections: HKU\S-1-5-21-842925246-1425521274-308236825-500\Software\Microsoft\windows\CurrentVersion\Internet Settings\Connections info SavedLegacySettings 0x3c0000001600000001000000000000000000000000000000040000000000
Blacklisted Malicious Spam Spoofing
My personal likely verdict is a "File Splitting Misinterpretation", so false positive,
polonus
