<p>steghide is a mature GPL-licensed CLI tool for hiding arbitrary data inside of of image files (and some archaic audio formats). Its official web presence is located at <ahref="https://steghide.sourceforge.net/">https://steghide.sourceforge.net/</a>. it conceals data inside a larger coverfile in a way that is indistinguishable to first-order statistical analysis. This means there is are anomalies in the file histogram, making most pictures innocuous <b>without having the original image to compare it to.</b></p>
<p>steghide is ubiquitously mirrored in various repositories and package managers. You can also find a clone of the sourceforge repository <ahref="https://github.com/StegHigh/steghide">on GitHub</a>. If you use APT, simply install it with</p>
<p>steghide uses subcommands, and the three most important ones are <codeclass="nim">info</code>, <codeclass="nim">embed</code> and <codeclass="nim">extract</code> which will be explained in sequence. For this tutorial, we are going to use the <ahref="https://apod.nasa.gov/apod/ap240824.html">Astronomy Picture of the Day of 2024-08-24</a>, a beautiful image of the anti-twilight arch:</p>
<p>Our example file to hide is going to be <ahref="https://bitcoin.org/bitcoin.pdf">Bitcoin: A Peer-to-Peer Electronic Cash System</a>, the original paper by Satoshi Nakamoto.</p>
<p>As mentioned above, the cover image must be larger than the file you wish to embed, <b>as a rule of thumb your coverfile should be 20 times larger</b>. (Hint: you can split larger files with tools like tar or 7z into smaller fragments to embed into a whole collection of cover files.) We can check how many bytes steghide can embed by using <codeclass="nim">steghide info <i>file</i></code>. In our case, it tells us that it can embed 232 KB and asks whether an attempt should be made at reading embed data without extracting. As there is nothing embedded yet, we decline with <kbd>n</kbd>.</p>
<p>The PDF is only 180 KB, so it fits. Next, we use <codeclass="nim">steghide embed -cf <i>coverfile</i> -ef <i>embedfile</i> -sf <i>destination</i></code> and get asked for a passphrase (make sure to remember it or safe it in a password manager). After re-entering the passphrase (you can set it beforehand with the <codeclass="nim">-p</code> option) it will write the processed file to the specified destination. You can also leave out the <codeclass="nim">-sf</code> option, in which case it defaults to overwriting the coverfile. Look at it and try to find a visual difference to the original:</p>
<p>It's completely lost in the visual noise. As an experiment, let's try taking the difference of both images with a program like GIMP. This is what it looks like:</p>
<p>A difference of zero means a fully black pixel. Try zooming in and you'll see that only a few pixels are slightly lighter than black. These are the pixels that contain parts of your embedded file in their least significant bits.</p>
<div><b>WARNING: changing the output file in anyway will make the embedded file irretrievable. This is especially important for every form of lossy compression!</b></div>
<p>Now let's try to extract the file we've just hid. For this, use <codeclass="nim">steghide embed -sf <i>input</i></code></p>. This will prompt you for the passphrase. Enter it, and the contents will be extracted into the working directory. In our case we will be asked whether we want to overwrite the file with the same name that already exists. (You can suppress this warning with <codeclass="nim">-f</code> or by specifying an alternative output destination with <codeclass="nim">-xf</code>. Here, I used the later so we can confirm the files to be identical with md5sum:
<p>And they are! This concludes the basic introduction to steghide. Some advanced details follow below, but in most cases, reading the well-written man page suffices.</p>
<p>There are a couple of things you shouldn't do with steghide. Here a quick overview:</p>
<ol>
<li><p><b>Use strong passwords:</b> Always a given. The password to steghide can be brute-forced like every other password. <ahref="https://github.com/RickdeJager/stegseek">stegseek</a> can brute force 14 million passwords in under 2 seconds.</p></li>
<li><p><b>Use original images:</b> Known images can be easily double-checked against your cover files. If for example the Monero icon on your website is different to that included in the official press kit, that's suspicious, defeating the purpose of steganography. Make sure to only use this with originals only you are in possession of - in a pinch, adding an in-picture caption, resizing it, etc. offers plausible deniability, as different image editing programs are notoriously variant in handling pixel-level details.</p></li>
<li><p><b>Avoid images with little detail:</b> Images without pixel-level visual noise (e.g. diagrams, images of text, etc.) will have less hiding space, and become visible deteriorated when files are embedded. For demonstration purposes, compare <ahref="map.jpg">this map</a> with its <ahref="map_orig.jpg">original</a>, then look at <ahref="map_diff.jpg">their difference</a>. The embedded file was a mere 4286 B in size, yet these two files differ by 6693 B in size! (The password is left as a brute-forcing exercise for the reader.)</p></li>
<li><p><b>Avoid format conversions:</b> Even "lossless" conversions from one image format to another tend to be non-reversible, making it impossible to retrieve the hidden data. Remember that many popular websites compress all images uploaded to them to save on bandwidth, making them unsuitable for our purposes.</p></li>
<p>As you've seen, steghide needs a passphrase to embed and extract data. (Note: using an empty passphrase can lead to issues extracting.) This passphrase is used to both encrypt your file before embedding and to seed the PRNG by which it selects pixel positions for embedding data. By default, it uses AES-128. You should not rely on steghide for securing your data cryptographically (see the <ahref="../stegaography/index.html">introduction to steganography</a>), and when in doubt you can separately encrypt the file before embedding, but you may still want to change the used algorithm. For this, simply use <codeclass="nim">-e <i>algorithm</i><i>mode</i></code>. You can list all available modes with <codeclass="nim">steghide encinfo</code>. So as example, to embed our previous picture using AES-256 in cipher feedback mode, you would use this:</p>
<p>Since steghide works on arbitrary binary data, you can embed steghide's output into another picture, provided the size is sufficient. The 4.8 MB picture below contains a 260 KB waveform audio file which in turns contains 2.7 KB UTF-8 encoded text file. (The passphrase is <kbd>moon</kbd> for both.)</p>
