[Showcase] PluginPatcher - Quick infected plugins - Might release
Okay so since im intrested in learning about BCEL(https://commons.apache.org/proper/commons-bcel/) I decided to learn it by making sumthing I kinda need so I decided to make a infected plugin maker 
So this program is still pretty buggy but it works almost 99% just some little bugs. What it does is you select a plugin then it will do crazy stuff and find the main plugin class. Then it will do the magic with bcel and inject 1 line of code at the start of the onEnable method. Then it dumps the new main plugin class. After that I can put in my lib for infected plugins and simply drag in the patched class file and I got a infected plugin
Pics:
Patcher program in the eclipse console: Screenshot by Lightshot
Looking at the patched class via jd-gui: Screenshot by Lightshot it also adds the needed imports to the class file
It's basic stuff with bcel but I think it's epic :3
More info:
If main class couldn't be found in plugin.yml cause the file is bigger than the buffer it will loop through the class files in the jar and check if it extends JavaPlugin. Then it loops through the methods and looks for a onEnable/preEnable method else it shuts down. Then it adds the instructions and sets everything back and dumps the class :3
ps: I know I need to change the console output text lol
So this program is still pretty buggy but it works almost 99% just some little bugs. What it does is you select a plugin then it will do crazy stuff and find the main plugin class. Then it will do the magic with bcel and inject 1 line of code at the start of the onEnable method. Then it dumps the new main plugin class. After that I can put in my lib for infected plugins and simply drag in the patched class file and I got a infected plugin
Pics:
Patcher program in the eclipse console: Screenshot by Lightshot
Looking at the patched class via jd-gui: Screenshot by Lightshot it also adds the needed imports to the class file
It's basic stuff with bcel but I think it's epic :3
More info:
If main class couldn't be found in plugin.yml cause the file is bigger than the buffer it will loop through the class files in the jar and check if it extends JavaPlugin. Then it loops through the methods and looks for a onEnable/preEnable method else it shuts down. Then it adds the instructions and sets everything back and dumps the class :3
ps: I know I need to change the console output text lol
Originally Posted by Domokun_index
