"A-Team" Hacker Group Posts Purported Identities and Locations of LulzSec Members

A group calling itself the A-Team has posted what they contend are the names, locations, aliases and even family members of the hacking cabal known as LulzSec. Could this be the real reason the high-profile hacking group disbanded this weekend?

Listening to A-Team tell the story, there is no love lost between this new hacking crew and whoever it is ends up being the real people behind now-disbanded group LulzSec (and related group gn0sis):

The problem with Lulzsec/gn0sis's "Hacktivist" mantra is that they lack the skills to keep it going. As such after SONY they couldn't get into anything. So they switched their focus to just releasing random crap that didn't mean anything. Then they started running out of things they could hack. So they put out requests for people to join them. That got them a few hits, and now they've switched their gears again to be "ANTI-SEC". Whether or not this was an attempt at bring other groups out of the shadows (el8, h0no, zf0, etc), you can only speculate. But as of this writing: 6/24/2011 Sabu and Topiary are the only two people updating the twitter and releasing shit. Kayla is MIA. The gn0sis kids are gone in hiding somewhere.

From what we've seen these lulzsec/gn0sis kids aren't really that good at hacking. They troll the internet and search for sqlinjection vulnerabilities as well as Remote File Include/Local File Include bugs. Once found they try to download databases or pull down usernames and passwords. Their releases have nothing to do with their goals or their lulz. It's purely based on whatever they find with their "google hacking" queries and then release it.

The timing of this data dump and the abrupt LulzSec "retirement" Saturday are indeed curious. I suppose if a number of high-profile arrests are made in the near future concerning teens and twenty-something computer experts we'll know if this list is legit or not, huh? [Pastebin - Thanks, Adam]


You can keep up with YOUR NAME HERE, the author of this post, on Twitter[link to your account] or Facebook[link to your author page].