CREATING INFECTED IMAGES [ FATAL IMAGES] [ INJECT PAYLOAD]:D

[CrankDaddy]

# cd pixload Usage:
If you work with default data and there is no arbitrary output file, then next generation, such a file will be overwritten.
If there is a downloaded arbitrary output file, then indicate the name of the output, and the load will be written to it.
For convenience, place such a file in the tool directory.
1) For BMP files # ./bmp.pl -output file.bmp
2) For JPG 2, the type of load is either in the COMMENT parameter or DQT table
And for this type of file there is a load limit of 64 bytes and the requirement that the file be arbitrary.
./jpg.pl -place DQT -output file.jpg
./jpg.pl -place COM -output file.jpg
3) For PNG # ./png.pl -output file.png
4) For GIF # ./gif. pl -output file.gif
After generating the payload, the size in the properties will remain unchanged, but the image itself will take a minimum size.
Such files are dangerous for visitors to resources that have, in particular, an XSS vulnerability. For example, vulnerable resources are found in this way.
The presence of vulnerability allows even a loved one to bring to the main page.
Files are uploaded if allowed and an attack is performed through browsers when interacting with the file. Of course, we will not load anything anywhere and engage in sabotage.
Protection against such an attack is still controlled by javascript in the browser due to add-ons.
And when studying the file with a hex editor, or better, a packet analyzer, you can immediately see that something is wrong with the file and the script is visible in it