Hallo Leute,
Ein netter Fund den Ich heute gemacht habe.
----------------------------------------------------------------------------
Introducing worlds first League of Legends packet sniffer, sender and spoofer!
It is capable of:-
* Logging and naming the packets correctly
* Sending packets to the server and spoofing packets to the client
* Flooding a lot of text messages at once to lag everyone in the game
Instructions
Displaying certain packets
In order to log certain packets, you type '.show [ID]' - without the ' and the [] signs. ID represents the heximal packet id. A list of all packets has been attached in the release.
Displaying all packets
A command called '.showall' exists. If passed with no argument, it will show all outgoing and incoming packets. However, you can type '.showall send' or '.showall recv' if you want to either see only incoming or outgoing data.
Turning verbose off and log packets to a file
Logging packets to the chat window is very CPU intensive, blame the authors of the engine. Everytime you add a chat message, it eats up a lot of CPU cycles. Packets can be logged to a log file and the verbose can be turned off.
Simply time '.verbose off' and '.log on'. The log file can be set aswell, with '.log [FileName]'.
Sending packets
You will want to send manipulated packets to figure out how they could affect the game. Unfortunately it's not as easy as it used to be in other games as the send function requires two additional parameters. Arg1 and Arg2. I havn't bothered checking out what their real name is, however you have to pass those aswell. I guess one could just dump the values of those arguments for all packets.
However, once you have logged a few packets, you will notice that Arg1 and Arg2 is also being logged.
Sample output of the chat pkt:
C->S PKT_Dummy(00) 19 Arg1: 5 Arg2: 0
00 00 00 00 01 00 00 00 06 00 00 00 68 65 68 65 68 65 00
Arg1 in this case is 5 and Arg2 is 0. So if we want to send that packet, we type
'.send 5 0 00 00 00 00 01 00 00 00 06 00 00 00 68 65 68 65 68 65 00'
The result will look like this:
[Only registered and activated users can see links. Click Here To Register...]
Spoofing packets
Packets can be spoofed to the client with the command '.recv'. It's similar to .send, altho you don't need to pass any other arguments bysides just the packet.
e.g. '.recv A0 00 00 00 00 49 F5 6C' will open the AFK warning.
Hiding certain packets when using 'showall'
You can hide certain packets when using the showall command. Simply type '.hide [ID]'. It's suggested to hide out the packets BD and BE as they seem to be send frequently.
CommandList:
.show [id]
.hide [id]
.showall
.hideall
.clear
.log
.flood
.verbose
.send
.recv
.block
.unblock
If you have any questions, feel free to ask. Yes, I know - right now it's a pain in the ass to enter packets. However, I will try to come up with a solution to that. Perhaps allow you to paste stuff into the chat input.
Ein netter Fund den Ich heute gemacht habe.
----------------------------------------------------------------------------
Introducing worlds first League of Legends packet sniffer, sender and spoofer!
It is capable of:-
* Logging and naming the packets correctly
* Sending packets to the server and spoofing packets to the client
* Flooding a lot of text messages at once to lag everyone in the game
Instructions
Displaying certain packets
In order to log certain packets, you type '.show [ID]' - without the ' and the [] signs. ID represents the heximal packet id. A list of all packets has been attached in the release.
Displaying all packets
A command called '.showall' exists. If passed with no argument, it will show all outgoing and incoming packets. However, you can type '.showall send' or '.showall recv' if you want to either see only incoming or outgoing data.
Turning verbose off and log packets to a file
Logging packets to the chat window is very CPU intensive, blame the authors of the engine. Everytime you add a chat message, it eats up a lot of CPU cycles. Packets can be logged to a log file and the verbose can be turned off.
Simply time '.verbose off' and '.log on'. The log file can be set aswell, with '.log [FileName]'.
Sending packets
You will want to send manipulated packets to figure out how they could affect the game. Unfortunately it's not as easy as it used to be in other games as the send function requires two additional parameters. Arg1 and Arg2. I havn't bothered checking out what their real name is, however you have to pass those aswell. I guess one could just dump the values of those arguments for all packets.
However, once you have logged a few packets, you will notice that Arg1 and Arg2 is also being logged.
Sample output of the chat pkt:
C->S PKT_Dummy(00) 19 Arg1: 5 Arg2: 0
00 00 00 00 01 00 00 00 06 00 00 00 68 65 68 65 68 65 00
Arg1 in this case is 5 and Arg2 is 0. So if we want to send that packet, we type
'.send 5 0 00 00 00 00 01 00 00 00 06 00 00 00 68 65 68 65 68 65 00'
The result will look like this:
[Only registered and activated users can see links. Click Here To Register...]
Spoofing packets
Packets can be spoofed to the client with the command '.recv'. It's similar to .send, altho you don't need to pass any other arguments bysides just the packet.
e.g. '.recv A0 00 00 00 00 49 F5 6C' will open the AFK warning.
Hiding certain packets when using 'showall'
You can hide certain packets when using the showall command. Simply type '.hide [ID]'. It's suggested to hide out the packets BD and BE as they seem to be send frequently.
CommandList:
.show [id]
.hide [id]
.showall
.hideall
.clear
.log
.flood
.verbose
.send
.recv
.block
.unblock
If you have any questions, feel free to ask. Yes, I know - right now it's a pain in the ass to enter packets. However, I will try to come up with a solution to that. Perhaps allow you to paste stuff into the chat input.
