this next session will talk about injecting files, images, and interacting with payloads alot of this section is short and does not need exploration or even experience to understand hope it is easy for you.

---

> inject gif This command belongs to the stegonography segment of red rabbit, this command allows the user to inject a payload into a given GIF image/short video. If the image is not real path, or does not exist there are backend systems to run and generate a customized GIF based on the name that was not found or could not be opened that you inputted as a path. in the example below when you inject your image you are shown whjat you injected, the path to the image, the exif table, and the hex code showing the location of the GIF

---

> inject jpg, webp, bmp All of these commands inject jpg inject webp inject bmp all do the same exact thing, inject a payload into an image is the basis of all four of these commands

---

> inject png This command is apart of the stegonography toolkit and section that red rabbit holds, however this module is very very much different than any of the other stegonography modules and toolkits that red rabbit has in its selection. This image injection module is still being upgraded since it was built on a module written by the authors of the black hat go book, credits to them for such an amazing oppurtinity to inspire my team to look into stegonography and even modify the toolkit they taught us to build that i implimented into the red rabbit project. Currently this module can do a few things such as- -> Inject a simple payload into a PNG image -> Inject a encoded payload into a PNG image -> decode a payload in a PNG image -> Get meta and image information on the PNG image This toolkit also inspired some other things such as stegonography with archives which we will discuss next inject png is just one command however it has a few flags that can be used with it, in order to properly use this command and sucessfully inject your payload into the PNG image you must do a few things like specifying flags, for the most common usage of this script you can run the following Running script without being compiled | sudo go run main.go -i="path/to/image/image.png" -o="output_of_injected_image.png" --payload="some_payloas-02394890234890238904238904238904809342" Running script in binary form sudo ./main -i="path/to/image/image.png" -o="output_of_injected_image.png" --payload="some_payloas-02394890234890238904238904238904809342" example output below of a simple injection being made to a PNG image

---

> inject payload && inject payloadl && inject payloadul First off im going to start this by saying all three of these commands are the same but they are ran differently such as using different methods to encode the payload or embed the payload into a URL now a simple example of what this does is takes the payload you enter or a list of payloads and will inject it into the header of the URL, not the response header but the head of the URL so your URL will go from http://www.example.com -> http://www.example.com?=%3Cscript%3Ealert%28%29%3C%2Fscript%3E simple payload parsing at its finest, however there are very few ways of doing this such as the other two methods we have. The first command "inject payload" will just ask the user for a URL and a payload then simply parse the URL with the payload the next one which is payloadul will take a list of URL's and parse it with a given payload you tend to input or use, making the output something like this the last and final one "inject payloadl" will take a list of PAYLOADS and parse it into a given URL, an example output of this would be the following below, if your list is wack and not structures properly it may result in a poor output like the following