Join our community

It's easy to create unintentional-looking (JFIF-formatted) corrupted image files by overwriting the code stream identifier byte (at offset 0x44, after image data entry point) to any other value. Checking that it's the right byte is also easy, its value is 0x21 (! in ASCII) in the file's hex data.

glitchart @akuankka128 Source

It's easy to create unintentional-looking (JFIF-formatted) corrupted image files by overwriting the code stream identifier byte (at offset 0x44, after image data entry point) to any other value. Checking that it's the right byte is also easy, its value is 0x21 (! in ASCII) in the file's hex data.