Brute.Fail: Watch brute force attacks fail in real time
1–10 of 268 posts
Re: Brute.Fail: Watch brute force attacks fail in real time
#2This is fun to watch, seeing all the passwords is pretty interesting.
Just curious, why x out the IP at all?
Re: Brute.Fail: Watch brute force attacks fail in real time
#3Seems like some of them are residential IP addresses! I guess parts of a botnet or a compromised device?
Re: Brute.Fail: Watch brute force attacks fail in real time
#4This is fun to watch, seeing all the passwords is pretty interesting. Just curious, why x out the IP at all?
Presumably many brute force attempts come from compromised residential PCs, whose owners may not be aware that they are participating in an attack. It's not especially polite to expose all of that personal info.
Re: Brute.Fail: Watch brute force attacks fail in real time
#5Man, that one Brazilian IP really going hard
Re: Brute.Fail: Watch brute force attacks fail in real time
#6This is fun to watch, seeing all the passwords is pretty interesting. Just curious, why x out the IP at all?
> Just curious, why x out the IP at all?
Trying to avoid being a jerk. The sources are likely hacked boxes where the owner has no idea.
Re: Brute.Fail: Watch brute force attacks fail in real time
#7That’s neat. What’s the total volume per day? Are the passwords themselves being escaped in the final UI rendering? Otherwise you’d have an XSS for a password like “/* code */".
EDIT: Unless it's happening on the server side where it's being saved, I don't think they're being escaped:
col1.innerHTML = ' ' + msg.src;
col2.innerHTML = msg.proto;
col3.innerHTML = '' + msg.u + '';
col4.innerHTML = '' + msg.p + '';Re: Brute.Fail: Watch brute force attacks fail in real time
#8Seems like some of them are residential IP addresses! I guess parts of a botnet or a compromised device?
Internet of things.
Lets put 20 unpatched linux computers on every network and see how that goes.
Re: Brute.Fail: Watch brute force attacks fail in real time
#9I kinda want to know the server's address so I can send a "hello_hn" message in the passwords there.
Re: Brute.Fail: Watch brute force attacks fail in real time
#10That’s neat. What’s the total volume per day? Are the passwords themselves being escaped in the final UI rendering? Otherwise you’d have an XSS for a password like “ /* code */ ". EDIT: Unless it's happening on the server side where it's being saved, I don't think they're being escaped: col1.innerHTML = ' ' + msg.src; col2.innerHTML = msg.proto; col3.innerHTML = ' ' + msg.u + ' '; col4.innerHTML = ' ' + msg.p + ' ';
It is escaped server side. Anything long enough to be a useful payload is trimmed.