Community


Spotlight.

Week of 2026-11-15



Challenges

Steghide

steghide is a steganography program that is able to hide data in various kinds of image and audio files. The JPEG, BMP, WAV and AU file formats are supported for use as a cover file. There are no restrictions on the format of the secret data.

Overview: how does it work?

The secret data is first compressed and encrypted. The passphrase then seeds a pseudo-random number generator, which picks out a sequence of pixel positions in the cover file, this is where the data could go. Positions that already happen to hold the right value by chance are skipped. For the rest, a graph-matching algorithm pairs up positions so the data can be embedded by swapping their values with each other, rather than overwriting them, any leftover positions that can't be paired are overwritten directly instead.

This is the actual explanation steghide documents in its man page, it's genuinely a bit dense, so I'd recommend reading man steghide directly if you want the full technical detail rather than relying on a summary.

Example of how you can hide data using steghide:

_> steghide embed -cf test.jpeg -ef sec.txt -sf hidden.jpg
Enter passphrase:
Re-Enter passphrase:
embedding "sec.txt" in "test.jpeg"... done
writing stego file "hidden.jpg"... done

-ef, --embedfile, specify the file that will be embedded (the file that contains the secret message)

-cf, --coverfile, specify the cover file that will be used to embed data. The cover file must be in one of the following formats: AU, BMP, JPEG, or WAV.

-sf, --stegofile, specify the name for the stego file that will be created.

Get info about a file: steghide info file_name

_> steghide info hidden.jpg
"hidden.jpg":
  format: jpeg
  capacity: 3.9 KB
Try to get information about embedded data? (y/n) y
Enter passphrase:
  embedded file "sec.txt":
    size: 17.0 Byte
    encrypted: rijndael-128, cbc
    compressed: yes

Extract a hidden file: steghide extract -sf file_name

_> steghide extract -sf hidden.jpg
Enter passphrase:
wrote extracted data to "sec.txt".

_> cat sec.txt
I know kung fu: Show me.

Use steghide to extract the secret hidden inside /challenge/image.jpg.

It will ask for a passphrase, sometimes Enter alone can do the job.

The password is wrapped in steghide{}.

Once you find it, run /challenge/check and enter the password to get the flag.

Going Further

Check out man steghide for more information.

Let's start with the basics!

You interact with DOS using the commandline. I'm sure you're quite familiar with cat /flag in Linux (and if not, you can learn it!). In DOS, the cat equivalent is type. Like cat's default usage, type types out the file contents to the screen.

Let's dig in! The flag is in the flag.txt file of the C: drive. What the heck is the C drive? Roughly speaking, it's the DOS equivalent of /: it's the primary disk of the machine. The top-level directory of the C: drive is where DOS puts you when it boots up:

Booting from Hard Disk...
Starting MS-DOS...

C:\>

That prompt means:

  • C:: you are in the C: drive
  • \: you are in the top-level directory (yes, DOS uses \ instead of / for directory separators!!!)
  • > : this is the end of the prompt

Since you're already in C:\ and the flag is in C:\flag.txt, you can, like in Linux, just refer to it here as flag.txt. So, boot up your DOS (using /challenge/launch), and read the flag!


NOTE: This challenge requires a GUI to interact with the DOS machine, and so must be accessed through the desktop interface.

*NOTE: You can't select text directly from DOS! That technology simply didn't exist. However, you can use the "copy" functionality on the challenge Text User Interface to copy the whole screen to the clopboard, and extract the flag from there!

HTML is much more versatile than just altering a webpage's front end---it is also possible to embed Javascript within it. In this challenge, your goal is just that. You will need to formulate some message that sends out the alert Class is Canceled! then run the victim script.

⚔️ The Final Commission

The repository was still open on one tab. On another: a dungeon game, unlisted, no author credited. He loaded it mostly out of habit, the way you pick up something small when something large has just landed.

The roster populated with faces he knew. Bessie. Roen. Echo and Ohce. Pip, with circuit-light paws, electric blue visor, filed under Companion. And at the top of the list, ears and all: himself.

He couldn’t fight. He could only recruit.

He sent them in every order against the Warden at the bottom of the dungeon, a figure that the game had clearly not designed to fall. It didn’t matter who went first. The moment the Warden took his turn, they were gone. Pip, Bessie, the twins, all of them. One round each, no exceptions.

He sat back.

In the corner of the lowest floor, half-hidden behind a pillar, sat a merchant. Small table. One item in stock: a relic, unfinished, no name struck into it yet. Waiting.

Price: 1337 gold.

His tail flicked once.

“One last deal,” he said.

ROT13 recorre cada letra 13 posiciones en el abecedario (a → n, b → o...). Como el abecedario tiene 26 letras, aplicarlo dos veces te regresa al texto original.

codecs.py aplica ROT13 con rot13:

hacker@dojo:~$ python3 /challenge/codecs.py rot13 "texto"

Aplica rot13 al contenido de ~/flag para encontrar la flag.

Lānaʻi

  • Category: retro, pwn, VAX
  • Author: adamd

Lānaʻi, an island thought to be frozen in time. Journey into the past...

While perusing old ACSAC papers a portal appears, and you're teleported back to November 1st, 1988.

The Morris Worm is about to wreck havoc on the nascent ARPA-net.

Show that you have what it take to recreate the Morris Worm (which of course you'll use to fix the underlying software)!

Use /challenge/run to run a version of the challenge with the flag that listens on port 79.

Use /challenge/run-no-flag to run the challenge without the flag, use user root to login and poke around.

Luckily you brought with you this classic paper.

Set a register to a large value.

The ultimate shell script sanitizer is in /challenge/run. Can you bypass it?


WANT MORE? Check out The Art of the Shell to prove your shell mastery!

You are provided an emulated DIR-868L. Attempt to exploit the firmware with CVE-2017-14948.
Implement your exploit at /home/hacker/run_attack. The emulated target is provided for you; execute run qemu to start it. Once you see the "Emulation started" message, you may execute run check to test your exploit. Like in emulation, run check waits for your script, /home/hacker/run_attack, to exit before it runs the SLA checker. The SLA checker expects that the C2 follow-on in a good state and it can send commands right away.


30-Day Scoreboard:

This scoreboard reflects solves for challenges in this module after the module launched in this dojo.

Rank Hacker Badges Score