You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have benefited a lot from reading your newly modified code. There is a small demand, corresponding to the windows system, and the generated agent.exe has a size of 10 megabytes. Whether it can support the generation of smaller Trojan horses in the future only requires the function of uploading and downloading files and executing system commands. Because shellcode generation is not supported for the time being,I wonder if the Trojan can be made smaller so as to better perform the subsequent bypass AV operations.
The text was updated successfully, but these errors were encountered:
jm33-m0
changed the title
Whether it can support the generation of smaller Trojan horses in the future ?
Reduce agent binary size
Sep 13, 2022
Thanks. The resulting binary file can be packed with UPX so you may end up with 5MB or so.
Shellcode can act as a downloader so you can better stage your operation. For example you can write shellcode that downloads a PE loader, then the PE loader can download the actual agent binary and load it into its own memory space.
I have benefited a lot from reading your newly modified code. There is a small demand, corresponding to the windows system, and the generated agent.exe has a size of 10 megabytes. Whether it can support the generation of smaller Trojan horses in the future only requires the function of uploading and downloading files and executing system commands. Because shellcode generation is not supported for the time being,I wonder if the Trojan can be made smaller so as to better perform the subsequent bypass AV operations.
The text was updated successfully, but these errors were encountered: