Really nice! I appreciate this work!
It really keeps annoying me trying to find a real confirmable technique shutting down my agent.
Due to my hacking tools, I was not able to crash my agent nor setting my gateway to "Check" state.
Tho, it is crashing the "SroGuard_Game.exe"
People are partly able to log in, even if the "SroGuard_Game.exe" has been shut down.
Afterwards, reDDoSing the same port with the same methode - will show my a denied and wrong login, which obviously is correct, since the fake port of 15779 isn't the real one.
Edit:
Crashing the SroGuard_Game.exe will stop the server working ... any possibility avoiding this issue, crashing the "SroGuard_Game.exe"?
Blocking the fake ports (15779 and 15884) or even the real ports via Windows Firewall and Kaspersky ain't working. My tools are still crashing your guard.
Tho, could it be that this crashing is caused simply ... that I am on the same root?
Port checking shows that these ports are blocked and not accessible.
Hm, anyways...
Additionals:
I would like to request another issue:
Is there a possibility checking people's clients on, which kind of "client" they are logging into the server?
E.g. if someone uses PetFilter (Grab Pet tool, I am using it myself, since the grab function built inside the v188 client is awful and missing quite 50% of items), or mBot, or SBot, etc.
Would it possible checking the signature and packages?