So, word on the street is that you have your server ALMOST FUD, but you have one detection stumping you. And that detection is Avira TR/Dropper.gen
How can I get past this bugger?
1) The easiest and simplist way to do so is encrypt your server with an after-market obfusicator / packer. (SmartAssembly, xenocode, etc..)
2) Check to make sure "Stub" is NOWHERE in your code. I had my server's solution named "Stub", and matter or fact, that is what was causing the detection. Change it to something like "service"
3) Use complex filesplits, such as "ïu¾‹Ç¨Õ®ipfx'f趷Íîªý". A good way to get GOOD filesplits is to open another exe in notepad, and copy/paste some of the giberish you see (be sure to rearrange it a bit). Some AV's check for the word SPLIT, FILESPLIT, SPLITTER, etc..
4) Add junk code / Add 200kb icon. These are the 2 methods I absolutely hate, because you are not only not learning how to solve problems, but you are now stuck with a HUGE stub. No stub should EVER be over 25 - 30 kb. I like having mine under 20kb, and a 200kb icon prevents that! Although they CAN make your stub FUD.
5) Stop using EOF. Avira has started to pick up on EOF, and if your file is under like 50kb, and has EOF data, it will USUALLY be picked up as a dropper. How can I prevent using EOF? Check into other methods, such as http settings files (store your settings on a server and get the stub to download it!) or use UpdateResources (HERE)
If you still can't get it to compile FUD, you will have to start the trial/error method. To do this, remove a sub from your exe, compile it, and scan it. I suggest using Avira home, as it is MUCH faster than using a web based scanner (You know you are trying to beat avira, nothing else). When you come upon the detected line(s), try rearranging them, inversing if's, etc. Do what you have to do to make it different.
That's all folks. I will update this thread if I think of any other methods.
Thanks for reading!
How can I get past this bugger?
1) The easiest and simplist way to do so is encrypt your server with an after-market obfusicator / packer. (SmartAssembly, xenocode, etc..)
2) Check to make sure "Stub" is NOWHERE in your code. I had my server's solution named "Stub", and matter or fact, that is what was causing the detection. Change it to something like "service"
3) Use complex filesplits, such as "ïu¾‹Ç¨Õ®ipfx'f趷Íîªý". A good way to get GOOD filesplits is to open another exe in notepad, and copy/paste some of the giberish you see (be sure to rearrange it a bit). Some AV's check for the word SPLIT, FILESPLIT, SPLITTER, etc..
4) Add junk code / Add 200kb icon. These are the 2 methods I absolutely hate, because you are not only not learning how to solve problems, but you are now stuck with a HUGE stub. No stub should EVER be over 25 - 30 kb. I like having mine under 20kb, and a 200kb icon prevents that! Although they CAN make your stub FUD.
5) Stop using EOF. Avira has started to pick up on EOF, and if your file is under like 50kb, and has EOF data, it will USUALLY be picked up as a dropper. How can I prevent using EOF? Check into other methods, such as http settings files (store your settings on a server and get the stub to download it!) or use UpdateResources (HERE)
If you still can't get it to compile FUD, you will have to start the trial/error method. To do this, remove a sub from your exe, compile it, and scan it. I suggest using Avira home, as it is MUCH faster than using a web based scanner (You know you are trying to beat avira, nothing else). When you come upon the detected line(s), try rearranging them, inversing if's, etc. Do what you have to do to make it different.
That's all folks. I will update this thread if I think of any other methods.
Thanks for reading!
