Topic: EXE File Steganography

by alcopaul (@thealcopaul in Twitter)
12/28/2016


Data files like pdf, doc, jpeg, mp3, wmv and other files are an obvious curiosity for information hackers. Why? They contain data
and we have seen people love hiding data in data. The tendency for this is that people will naturally look for "data"
concealed in data sources.

One way to subvert this is to hide data in not so obvious places. Like in EXE files.

People will just think that "Hey, it's an exe file. If I click it, my computer may have a rootkit or virus."

So people are cautious to click exe files.

And that's the perfect place to hide data.

Right Platform
--------------

Any programming language can be used to do this. But, in standard compiled language like C, say if we program an exe file to hide
data within itself, it could be in spaces within the exe file or appending the data to the file. Moreover, the file could include
extra, if not, mega bytes of code that will handle the encryption of data, resulting to a very big file.

Good thing that the .NET Framework Languages exists, for this is the perfect platform for us to do our aim.

.NET has classes that contain assymetric and symmetric encryption routines. Symmetric encryption alone could be used but communicating
paragraphs worth of text and for safer key exchange, assymetric encryption is preferable, combined with symmetric encryption.

Assymetric encryption can just encrypt small amounts of data. So for our purpose, we will use both. Encrypt the large data with
a random generated key with symmetric encryption and encrypt the key with assymetric encryption.

Crafting our EXE file
---------------------

For our exe file, It has to be a quine. Why? So it could compile itself, forming an exefile that looks like it's not tampered by
appending or space filling.

.NET framework has the ability to compile sources programmatically. And for the exe file to be recompiled, it has to reproduce
its own source code when it is run.

Thus it must be a quine.

What would our quine do?

Get the information on the console when say "/infohide" command-line is typed, generate a random key and use it to encrypt the message,
encrypt the key with a public key, attach the encrypted data and encrypted key to the source and recompile it to be an exe file.

e.g.

/infohide "This is my message to Rudy." <public key here>

Then send the exe file to the recipient.

Then the recipient executes the exe file to read the message, with another command-line.

e.g.

/readmsg <private key here>

say the "/readmsg" command-line just reads the data stored, decrypt the encrypted key with a private key and decrypt the message with
the decrypted key.


Those who will intercept the exe file would not notice the communication channel, and if attached to an email, would think that
the email came from a third party trying to infect the target with a virus. But i think that Gmail, Yahoo and the like banned
exe files in the attachments. Well, warez sites could be your communication platform now.

Thus another layer of security is made.

~end

[YHo]
@thealcopaul in Twitter

Thumbs up +1 Thumbs down

2 (edited by thesnark 2017-01-16 18:34:29)

Re: EXE File Steganography

As ridiculous as it might sound, doing an xor cipher on your exe file as a last step and doing stego inside of an image might take this concept all the way home.

I realize the obvious question might be: Why use stego for stego? If people find the exe, they will assume it is a virus and stop there. The message is still encrypted and the concept could be taken to places like gmail. Just a thought.

So the final channel might look like:

Shared xor(or AES if you're paranoid) key
Stored in image
Shared to imgur or gmail or whatever
public/private keypairs for exe crypto

Awesome post, thank you!

"For the Snark was a Boojum, you see."

Thumbs up Thumbs down

Re: EXE File Steganography

I did this with a key "generator" back when I was just a little hacklet. I didn't want bots to steal my keys, so I packed it all up into an executable.
No one downloaded it.

I like to examine and theorize about everything, from Amazon's <quote> impenetrable </quote> ultravisor to autorun viruses (virii?) being technology's version of an STD (Slot Transmitted Disease).
I dabble in Python 2.x and non-stereotypical BATCH (x>50 lines). I also fuck up VMs from time to time.

┬──┬ ︵ /(.□. \)

Thumbs up Thumbs down