> For the complete documentation index, see [llms.txt](https://centinels.gitbook.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://centinels.gitbook.io/home/writeups/n00bzctf/forensics-wave.md). # forensics/wave 387 points Writeup by Victor We're given what appears to be a corrupted .wav file. Media Player practically screams this if you try opening it and playing the audio. If you try to open the file normally in [Audacity](https://www.audacityteam.org/download/) (the best application for audio ctf challenges btw) it won't let you because, as hinted already, the file is corrupt. But there's one way to open corrupt files in Audacity: by importing the raw data of the file.

With the audio file successfully opened in Audacity, you should see something like this:

I wouldn't recommend clicking the play button (speaking from experience here). But what you should notice are the lengths of each audio segment. They're all either wide or thin, no in between. This should immediately scream out to you "MORSE CODE"!

As drawn at the bottom of the image, the morse could is "-... . . .--. -... --- .--. -- --- .-. ... . -.-. --- -.. ." and if you input that into a [morse code translator](https://morsecode.world/international/translator.html), you should get the output of "BEEPBOPMORSECODE".

Flag: `n00bz{beepbopmorsecode}` \*challenge tells you the text is in all lowercase --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://centinels.gitbook.io/home/writeups/n00bzctf/forensics-wave.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.