> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/useful-resources/forensics.md). # Forensics Forensics helper notes for steganography, Steghide, image recovery, and Depix workflows used in CTFs and offensive security labs. Small forensic helper notes for media files, hidden data, and image recovery tasks that appear in CTFs, labs, and practical investigations. ## Forensics Resources

:image:

Steganography - Steghide

Steghide steganography notes for extracting hidden files from images or audio, testing passphrases, and validating embedded data during CTFs.Steganography - Steghide

:image:

Depix Images

Depix image recovery notes for reversing pixelated text, preparing source images, running Depix, and validating recovered secrets during OSINT work.Depix Images
### Workflow 1. Identify whether the challenge involves hidden data, metadata, image artifacts, or visual redaction. 2. Try low-impact inspection first before destructive transformations. 3. Record exact commands, input files, output files, and recovered evidence. --- # 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://hacking-notes.jord4n.pro/useful-resources/forensics.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.