Trojan project

Greetings /prog/, I'm from a neighboring board.

I'm on the last phases of a trojan project. I'm having a hard time finding the best way of hiding my malicious executable within another executable. I assume the best way of doing that would involve assembly? "Code caves" seem to be what I'm looking for, though there doesn't seem to be much tutorials for it. Any advice? Thanks in advance.

>>34
So you basically encrypt what you say in the irc channel?
Pretty much.

How would this stop someone simply greping the readable characters in your executeable; and using this info find where your irc server is located and shut it down?
The trojan connects to several different servers, each of which don't belong to me. Simply knowing that it connects to random servers is not enough information to endanger it. What's more important is the channels it joins. If those were capable of being traced it would be problematic, hence the reason why this trojan uses several factors to determine which channels to join (and when to join them).

Also, there's no plain text sitting around in the code. All of the text is encrypted at compile-time and decrypted during run-time. In addition to some basic obfuscation, the executable is stripped of symbol tables. The words, fuck crackers; however, doesn't appear to be obfuscated. I'll have to patch this error in a future release.