<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Steganography on Akshit Kathuria</title>
    <link>https://ak-debug.github.io/tags/steganography/</link>
    <description>Recent content in Steganography on Akshit Kathuria</description>
    <image>
      <title>Akshit Kathuria</title>
      <url>https://ak-debug.github.io/social-preview.png</url>
      <link>https://ak-debug.github.io/social-preview.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 12 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://ak-debug.github.io/tags/steganography/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Image Forensics: Metadata, Hidden Dimensions, and Layer Analysis</title>
      <link>https://ak-debug.github.io/posts/image-forensics-metadata-and-hidden-dimensions/</link>
      <pubDate>Thu, 12 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://ak-debug.github.io/posts/image-forensics-metadata-and-hidden-dimensions/</guid>
      <description>An image can hide data in its header, in its metadata, or in the pixel values themselves. Here I cover three independent techniques for finding it: rewriting the dimensions in a JPEG&amp;rsquo;s SOF0 marker to reveal cropped-out rows, reading metadata with exiftool and decoding base64, and splitting an image into bit planes with Aperi&amp;rsquo;Solve. Three forensics challenges from the bi0s DD CTF serve as worked examples.</description>
    </item>
    <item>
      <title>Repairing Corrupted PNG Files by Hand</title>
      <link>https://ak-debug.github.io/posts/repairing-corrupted-png-files/</link>
      <pubDate>Thu, 12 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://ak-debug.github.io/posts/repairing-corrupted-png-files/</guid>
      <description>A PNG that refuses to open is rarely beyond repair. Its structure is simple: an 8-byte signature followed by length-type-data-CRC chunks. Once you know that layout, you can fix a broken file in a hex editor. Here I walk through repairing a mangled signature, IHDR header, chunk name, and CRC checksums, using two forensics challenges from the bi0s DD CTF as worked examples.</description>
    </item>
    <item>
      <title>Steganography: Finding Data Hidden in Images and Whitespace</title>
      <link>https://ak-debug.github.io/posts/steganography-extracting-hidden-data/</link>
      <pubDate>Thu, 12 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://ak-debug.github.io/posts/steganography-extracting-hidden-data/</guid>
      <description>Steganography hides data in plain sight, inside an ordinary image or an innocent-looking text file. This is a reference guide to the standard workflow: inspect a file with aperisolve, exiftool, binwalk, and strings; pull embedded data out of an image with steghide; brute-force an unknown passphrase with a wordlist; and detect and decode whitespace stego with stegsnow. Two forensics challenges from the bi0s DD CTF serve as worked examples.</description>
    </item>
  </channel>
</rss>
