Vulnerabilities / Threats
2/28/2013
10:16 AM
50%
50%

Anonymous: 10 Things We've Learned In 2013

The Anonymous hacker group continues to seek equal measures of revenge, justice and reform -- preferably through chaotic means -- for perceived wrongdoings.
Previous
1 of 10
Next


Anonymous continues to evolve. After launching online attacks against the Church of Scientology in 2008, Anonymous gained renewed energy with distributed denial-of-service (DDoS) attacks in 2010 against PayPal, MasterCard and other organizations it accused of blockading financial payments to WikiLeaks.

Since then, the loosely organized and chaos-loving hacktivist collective has continued stealing and dumping -- doxing -- data from businesses, government agencies and individuals that the group's members disliked, gaining further notoriety with high-profile breaches of HBGary Federal, private intelligence firm Strategic Intelligence (better known as Stratfor), consumer electronics giant Sony and even an FBI transatlantic cybercrime coordination call. Along the way, a limelight-seeking spinoff, LulzSec, and subsequent re-merger in the form of Operation AntiSec, helped further burnish the Anonymous brand.

At least, that is, until authorities caught up with alleged key members, leading to multiple arrests and convictions. Worst of all for Anonymous supporters, court documents revealed that founding father and LulzSec leader Sabu -- real name: Hector Xavier Monsegur -- had been busted by the FBI in June 2011 and within a day of his arrest turned informant. In short order, U.S. and British authorities claimed to have collared the ringleaders of the attacks launched against not just Sony and Stratfor, but numerous police departments and businesses. Far from being a group without a leader, authorities said, the Anonymous and LulzSec attacks had been carried out by a few key people, typically by exploiting known vulnerabilities in websites.

But with the alleged ringleaders facing jail time, the Anonymous brand didn't seem to suffer. Notably, Anonymous groups in specific geographies, including Mexico, South America, France and beyond, began promoting a more local and overtly political agenda.

In the United States, meanwhile, the group appeared to gain new impetus in January 2013, after Internet activist Aaron Swartz committed suicide. The co-founder of Reddit had been facing a potential jail sentence of at least 35 years after being arrested in 2011 for illegally gaining access to the JSTOR academic database and downloading millions of articles that had been funded by the U.S. government, and which he planned to post for free. Ultimately, he never did so, and after he agreed to unspecified damages, as well as to delete all of the data he'd downloaded, officials at JSTOR considered the case to be closed. Federal prosecutors and the Massachusetts Institute of Technology, however, pressed ahead, ultimately charging Swartz -- who'd long suffered from depression -- with 13 felony violations.

In the wake of Swartz's death, Anonymous focused its efforts on reforming an issue already near and dear to many members' hearts: The 1986 Computer Fraud and Abuse Act (CFAA) law that's often used to prosecute hackers, and punishing anyone it felt was responsible for contributing to Swartz's death. Cue website defacements and takedowns.

Read on to catch up on the latest Anonymous developments.

Photo courtesy of Flickr user Edans.

Previous
1 of 10
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Page 1 / 2   >   >>
EslamP248
50%
50%
EslamP248,
User Rank: Apprentice
8/15/2013 | 10:38:40 PM
re: Anonymous: 10 Things We've Learned In 2013
eslamp 248
EslamP248
50%
50%
EslamP248,
User Rank: Apprentice
8/15/2013 | 10:38:29 PM
re: Anonymous: 10 Things We've Learned In 2013
top covere pix
EslamP248
50%
50%
EslamP248,
User Rank: Apprentice
8/15/2013 | 10:38:11 PM
re: Anonymous: 10 Things We've Learned In 2013
my friends
EslamP248
50%
50%
EslamP248,
User Rank: Apprentice
8/15/2013 | 10:36:39 PM
re: Anonymous: 10 Things We've Learned In 2013
eslampop785
EslamP248
50%
50%
EslamP248,
User Rank: Apprentice
8/15/2013 | 10:36:30 PM
re: Anonymous: 10 Things We've Learned In 2013
eslampop
EslamP248
50%
50%
EslamP248,
User Rank: Apprentice
8/15/2013 | 10:14:14 PM
re: Anonymous: 10 Things We've Learned In 2013
facebook
majenkins
50%
50%
majenkins,
User Rank: Apprentice
4/24/2013 | 5:10:14 PM
re: Anonymous: 10 Things We've Learned In 2013
Revenge yes, justice only their own eyes, and reform only to remake the world to comform their ideas.
PJS880
50%
50%
PJS880,
User Rank: Ninja
3/14/2013 | 11:12:35 PM
re: Anonymous: 10 Things We've Learned In 2013
Great article but I have to agree with Leo, I dislike reading these articles for that reason alone. All though the topics are of interest, I donG«÷t have the patience. I also have to disagree with Jonathan on his views on people and their awareness about their online security. I believe because of all the attacks and breeches and the general publicG«÷s knowledge is constantly increasing, which was the exact opposite in the past.

Paul Sprague
InformationWeek Contributor
Jonathan_Camhi
50%
50%
Jonathan_Camhi,
User Rank: Apprentice
3/5/2013 | 9:47:33 PM
re: Anonymous: 10 Things We've Learned In 2013
I hadn't heard of this Rustle League incident before. Hackers hacking hackers. I wonder if all of the news surrounding hacking and cybercrime lately could put a big enough dent in people's trust in the internet to actually change people's behavior. Will people start taking their individual online security more seriously? Personally, I doubt it. I feel like we have already developed a sort of blind trust in the internet because it makes our lives so convenient that we don't even want to consider what would happen if our online credentials were compromised.
Leo Regulus
50%
50%
Leo Regulus,
User Rank: Apprentice
3/3/2013 | 8:54:42 PM
re: Anonymous: 10 Things We've Learned In 2013
Information Week only had one important New Year's Resolution this year. '"No Slide Show Articles with out a prominent 'View-as-one-page' link." How's that working out for you so far?
Page 1 / 2   >   >>
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-9710
Published: 2015-05-27
The Btrfs implementation in the Linux kernel before 3.19 does not ensure that the visible xattr state is consistent with a requested replacement, which allows local users to bypass intended ACL settings and gain privileges via standard filesystem operations (1) during an xattr-replacement time windo...

CVE-2014-9715
Published: 2015-05-27
include/net/netfilter/nf_conntrack_extend.h in the netfilter subsystem in the Linux kernel before 3.14.5 uses an insufficiently large data type for certain extension data, which allows local users to cause a denial of service (NULL pointer dereference and OOPS) via outbound network traffic that trig...

CVE-2015-2666
Published: 2015-05-27
Stack-based buffer overflow in the get_matching_model_microcode function in arch/x86/kernel/cpu/microcode/intel_early.c in the Linux kernel before 4.0 allows context-dependent attackers to gain privileges by constructing a crafted microcode header and leveraging root privileges for write access to t...

CVE-2015-2830
Published: 2015-05-27
arch/x86/kernel/entry_64.S in the Linux kernel before 3.19.2 does not prevent the TS_COMPAT flag from reaching a user-mode task, which might allow local users to bypass the seccomp or audit protection mechanism via a crafted application that uses the (1) fork or (2) close system call, as demonstrate...

CVE-2015-2922
Published: 2015-05-27
The ndisc_router_discovery function in net/ipv6/ndisc.c in the Neighbor Discovery (ND) protocol implementation in the IPv6 stack in the Linux kernel before 3.19.6 allows remote attackers to reconfigure a hop-limit setting via a small hop_limit value in a Router Advertisement (RA) message.

Dark Reading Radio
Archived Dark Reading Radio
After a serious cybersecurity incident, everyone will be looking to you for answers -- but youíll never have complete information and youíll never have enough time. So in those heated moments, when a business is on the brink of collapse, how will you and the rest of the board room executives respond?