Suck-O Time

Le lame et le fail. PDF Print E-mail
Written by bad_brain   
Tuesday, 19 February 2013 16:07

Awww.....now that was really pathetic my dear lamers at 78.115.120.170 and 93.14.235.121. How long your attack lasted before I sent your lame asses into 0-route land? 5 seconds? XD

 

https://www.youtube.com/watch?v=iGJSN5CgYoY

 

Comments  

 
#6 RE: Le lame et le fail. — bad_brain 2013-02-21 13:21
Quoting ph0bYx:
Please tell me you have the chat logs?

errrm...... :-*
I don't run any convo logs, neither locally nor on the server, but there were plenty of users on at the same time, so best ask one of the usual suspects, I am sure one of them has a log. ;)
 
 
#5 RE: Le lame et le fail. — ph0bYx 2013-02-21 13:08
Please tell me you have the chat logs?
 
 
#4 RE: Le lame et le fail. — bad_brain 2013-02-20 22:40
now with 100% more roflcopter:
obviously some lobotomy patient went to a french hacking site and acted as "owner of suck-o.com", saying we will attack them. the owner of that site came to IRC today and we had some good laughs about it. :D
 
 
#3 RE: Le lame et le fail. — bad_brain 2013-02-20 11:55
not just strange, it was simply retarded... :D
each of their silly requests was identified as "caused by bot", and so it didn't even made it to the actual site: no db activity, no server load.
damage caused: eating up 600MB of server space by bloating the access log. I am deeply impressed... :D
 
 
#2 RE: Le lame et le fail. — poppoob 2013-02-20 03:31
Lmao, that is strange!
 
 
#1 RE: Le lame et le fail. — bad_brain 2013-02-19 23:49
it gets even more pathetic. all in all it where about 10 hosts running the attack, all either in france or (french) africa. I didn't even noticed the other hosts until now, because the attack had no effect at all different than bloating the access logs... :D
a LITTLE strange is the visit from belgium right before the attack started....tsk tsk tsk...lousy amateurs...I am pretty sure someone is butthurt because of my latest article. get over it, loser. :D
 

Sorry, but you have to be registered and logged in to post comments.