Over the past six months various groups of relatively young hackers have been having their way with the internet at large, breaking into high profile websites, curiously targeting sites affiliated with government, corporations, and gaming – because naturally those three things usually go together.<\/p>\n
An older group of hackers know as The A-Team has managed to uncover the personal identities of LulzSec and Anonymous members thought to be responsible for a number of these hacks.<\/p>\n
“To understand who\/what lulzsec\/gn0sis are\/is you need to understand where they came from. Everything originates from the *chan (4chan\/711chan\/etc.) culture. This internet subculture is pretty much the dregs of the internet. It’s a culture built around the anonymity of the internet. If your anonymous no one can find you. No one can hurt you, so your invincable. The problem with this idealogy, is it’s on the internet. The internet by definition is not anonymous. Computers have to have attribution. If you trace something back far enough you can find its origins.” <\/em>– Official A-Team release. <\/a><\/p>\n The A-Team doesn’t think much of Lulzsec’s hacking abilities, saying, “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.”<\/p>\n The release goes on to list the full names, address, and other details for numerous hackers suposedly behind LulzSec and Anonymous, including “Sabu”, who according to unveiled chat logs, was the lynch pin behind many security attacks.<\/p>\n Incidentally, LulzSec announced over the weekend that they were done hacking<\/a> under the LulzSec banner, and the LulzSec twitter page<\/a> has for the first time in weeks been inactive for over 48 hours.<\/p>\n