hello evy body
The file dnetc518-w32-x86.exe to detect as malware@3nj4wpp0cm2p7, by COMODO I.S. 5.8 (last update in 21.10.2010)

---

-GPU-Z-

-F@H-

hello evy body
The file dnetc518-w32-x86.exe to detect as malware@3nj4wpp0cm2p7, by COMODO I.S. 5.8 (last update in 21.10.2010)

Give it a day or so, it is probably a false positive they usually are. One thing alot of us have done is to exclude the Boinc set of directories from the AV check, but keep every other directory to be checked. That way if it is a false positive, we won't know it, and if it really is a problem then when it expands beyond the Boinc directories it will be caught.

HALICE

566 Moo!Wrapper 23.10.2011 20:03:29 / [error] Signature verification error for dnetc518-win32-x86.exe
567 Moo!Wrapper 23.10.2011 20:03:29 / [error] Checksum or signature error for dnetc518-win32-x86.exe

---

-GPU-Z-

-F@H-

my av software is detecting it as a trojan as well

my av software is detecting it as a trojan as well

Is it just that file or others too? If just that one file then it is probably a false positive, no fun in making a virus that doesn't spread beyond itself!

both the cpu and gpu exe's are being detected as trojans

Trojan.Generic.KD.311346 detected in dnetc_1.02_windows_intelx86_ati14.exe

Trojan.Generic.KD.311346 detected in dnetc_1.2_windows_intelx86.exe

im usin an ISP provided AV suite and i cant manually add items to the exclude list :( but i ran through a bunch of tasks and no infections elsewhere in the pc. just it keeps deleting the exe's as soon as it detects them and is screwing up the WU's

both the cpu and gpu exe's are being detected as trojans

Trojan.Generic.KD.311346 detected in dnetc_1.02_windows_intelx86_ati14.exe

Trojan.Generic.KD.311346 detected in dnetc_1.2_windows_intelx86.exe

im usin an ISP provided AV suite and i cant manually add items to the exclude list :( but i ran through a bunch of tasks and no infections elsewhere in the pc. just it keeps deleting the exe's as soon as it detects them and is screwing up the WU's

Maybe you can contact Tech Support to figure out how to exclude directories, that is what most people do. They exclude the Boinc directories and then if it really is a problem catch it when it infects other parts of the pc.

The file dnetc518-w32-x86.exe to detect as malware@3nj4wpp0cm2p7, by COMODO I.S. 5.8 (last update in 21.10.2010)

D.net Client detections like this are what I was referring toin http://moowrap.net/forum_thread.php?id=104#921. There's not much I can do about those, unfortunately. :(

both the cpu and gpu exe's are being detected as trojans
Trojan.Generic.KD.311346 detected in dnetc_1.02_windows_intelx86_ati14.exe
Trojan.Generic.KD.311346 detected in dnetc_1.2_windows_intelx86.exe

But these are the wrapper application I compile and it seems to be doing something similar to what a some generic Trojan would do and thus gets flagged as suspicious. :( What I can do here is to recompile the wrapper and hope it doesn't match their signatures anymore. This and some additional fixes are what I'm working on for the v1.3 of the application.

Additionally, I would appreciate if somebody that get this detection could contact their AV vendor and ask what these samples do that their AV software consider suspicious. By knowing this I could try to make sure wrapper doesn't do that anymore in case the simple recompile isn't enough.

-w

The file dnetc518-w32-x86.exe to detect as malware@3nj4wpp0cm2p7, by COMODO I.S. 5.8 (last update in 21.10.2010)

D.net Client detections like this are what I was referring toin http://moowrap.net/forum_thread.php?id=104#921. There's not much I can do about those, unfortunately. :(

both the cpu and gpu exe's are being detected as trojans
Trojan.Generic.KD.311346 detected in dnetc_1.02_windows_intelx86_ati14.exe
Trojan.Generic.KD.311346 detected in dnetc_1.2_windows_intelx86.exe

But these are the wrapper application I compile and it seems to be doing something similar to what a some generic Trojan would do and thus gets flagged as suspicious. :( What I can do here is to recompile the wrapper and hope it doesn't match their signatures anymore. This and some additional fixes are what I'm working on for the v1.3 of the application.

Additionally, I would appreciate if somebody that get this detection could contact their AV vendor and ask what these samples do that their AV software consider suspicious. By knowing this I could try to make sure wrapper doesn't do that anymore in case the simple recompile isn't enough.

-w

Is that something Dr. David Anderson can help with?