LulzSec started out as the self-appointed online vigilance commission. Now, it has replaced Anon as the next organized hacker group taking down websites. Anonymous suffered a rift over leadership issues and went MIA. The Anon era might be past but its members and competitors are still out there and the most popular one of them th3j35t3r is not happy at LulzSec. LulzSec has pissed off almost everyone by now.
You all might remember th3j35t3r as the guy who was taking down WikiLeaks a few days back. The same th3j35t3r is blowing their cover as it can be seen in this Blogspot blog. He has published their chat logs from inside the IRC channels and has even gone so far as to expose some of those LulzSec members. The blogspot blog in question has entire conversations put up from IRC channels. As you read up the posts, you will numerous find individual profiles at the end of the blog as well with photographs and home addresses.
Clearly, no one finds the LulzSec lulzworthy anymore. They are trying desperately to cover their tracks with obvious methods, like encrypting drives and using Virtual private networks to stay behind closed doors. Let us see how far this level of anonymity works for them.
Another interesting observation in the expose is Barrett Brown of the (supposed) members of LulzSec who is a writer at Vanity Fair, Huffington Post and Onion. My understanding is that he is not really a LulzSec member and came into the crossfire when researching on something to write. Maybe he was just watching over the IRC like th3j35t3r. Whether this is th3j35t3r or not is well doubted but this blog makes one thing clear. LulzSec is a ruthless group hated by its own kind and pretty much everyone by now. You can follow this reddit discussion for continuous updates.
When on one hand Anon fights Sony and other corporates with their DDoS attacks, it is also fighting an internal war for leadership and control. AnonOps was the very control center of Anon, with all instructions and operations being directed from this IRC channel. Ryan, who was also assuming control as the top-level management at Anon was a moderator at the IRC channels.
This incident marks a clear rift in Anon. On one hand where there is a group of hackers who accept anyone wanting to fire up a LOIC and join in hacks while on the other hand, there is a closed faction consisting of uber hackers, who do not want to have anything to do with noobs.
The rift got bigger and now, Ryan is attacking AnonOps. Ryan has a significant amount of control over Anon as all AnonOps domains are registered in his name. He is also one of the mods on the AnonOps IRC channels that read “anonops dead go home” now. AnonOps might not be the only place where Anon meets, but it was their hot action center until now.
Though, while Ryan was taking down AnonOps with a DDoS himself, those on the AnonOps IRC were discussing plans to break free and go rouge. The democratic leaders at Anon have released a statement on Ryan’s actions saying,
We regret to inform you today that our network has been compromised by a former IRC-operator and fellow helper named “Ryan”. He decided that he didn’t like the leaderless command structure that AnonOps Network Admins use. So he organised a coup d’etat, with his “friends” at skidsr.us . Using the networks service bot “Zalgo” he scavenged the IP’s and passwords of all the network servers (including the hub) and then systematically aimed denial of service attacks at them (which is why the network has been unstable for the past week). Unfortunately he has control of the domain names AnonOps.ru (and possibly AnonOps.net, we don’t know at this stage) so we are unable to continue using them.
Anon is struggling internally for conflict of interest and trust issues. What happens behind those closed doors, stays well behind closed doors. We can speculate all we want. However, one thing is clear from here. Ryan is fighting Owen for leadership and control and this is breaking up Anon, exposing it pretty badly in the process.
You can head over to this self-explanatory website for the complete ego-clash logs. The (probable) story from AnonOps is told here.