If you are an anti-virus vendor, then you do this (or should do it!) before every release of your product, in order to ensure that it really works. Obviously, there is considerable intellectual justification for testing anti-virus software against real viruses. Your best response to a request from an unknown person is simply to decline politely.Ī third set of requests come from exactly the people you might think would be least likely to want viruses „users of anti-virus software“. They want some way of checking that they have deployed their software correctly, or of deliberately generating a „virus incident in order to test their corporate procedures, or of showing others in the organisation what they would see if they were hit by a virus“. There are relatively few laws (though some countries do have them) preventing the secure exchange of viruses between consenting individuals, though it is clearly irresponsible for you simply to make viruses available to anyone who asks.

Other requests come from people you have never heard from before.

Using strong encryption, you can send them what they have asked for by almost any medium (including across the Internet) without any real risk. Some requests are easy to deal with: they come from fellow-researchers whom you know well, and whom you trust. If you are active in the anti-virus research field, then you will regularly receive requests for virus samples.

(read the complete text, it contains important information) It was decided not to change the file itself for backward-compatibility reasons.

The content of this documentation (title-only) was adapted 1 September 2006 to add verification of the activity of anti-malware or anti-spyware products.

The definition of the file has been refined by Eddy Willems in cooperation with all vendors.

This file used to be named ducklin.htm or ducklin-html.htm or similar based on its original author Paul Ducklin and was made in cooperation with CARO.

Macos antimalware