You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected behavior
I'm not sure what result I should expect, perhaps that there was an error in the attack or that it was successful, but I sense that if unhandled errors are shown there must be a problem.
Hey thanks for the detailed report. Since it's hard to debug the issue from the posted traceback, let's try to narrow it down.
Did you try it on a different Target? Is it behaving similarly for all the targets?
Is the target actually going down when you are getting this error and then recovering quickly?
What are the logs on the server right at the moment you see this error on the client?
Are both client and server running on the same machine?
My gut feeling is that:
A. the target is actually going down and recovering immediately through some kind of self-healing load balancer.
B. There's an Anti-DDoS in place, which instead of sending an error response with a 400+ status code, it's actually closing the connection.
I can't tell if the site crashes and recovers quickly, since I refresh the page and it is still up, if it is something very fleeting I don't notice it.
I have posted logs.
Yes, both are on the same machine, I use cmder, server on one tab and client on the other.
In the flollowing target the script stuck in aiohttp.client_exceptions.ClientOSError: [WinError 10054] An existing connection has been forced broken by the remote host. and never ends.
I got some time to look through the logs but unfortunately, there's no concrete giveaway on what's the exact issue. However, judging purely based on the logs, the communication between Hulk Server and Hulk Client is breaking abruptly and not the actual request from Hulk Server to the target. I'll need to recreate the setup and test it myself to debug further. I'll update you once I get the time to do this.
Choose a Category:
Describe the bug
Always, after 500 attacks, errors appear on the console, and the one in the title is the exception that first shows up.
To Reproduce
Steps to reproduce the behavior:
hulk_launcher.exe server https://target.com
. Shows correctly info.hulk_launcher.exe client
. Start attack corectly.Expected behavior
I'm not sure what result I should expect, perhaps that there was an error in the attack or that it was successful, but I sense that if unhandled errors are shown there must be a problem.
Output
Console output (not complete, too large)
Desktop (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: