Feeds

Anonymous reverse ferrets on CIA.gov takedown

'We blacked out website merely reported the outage'

Remote control for virtualized desktops

Loosely connected hacking collective Anonymous claimed responsibility for making the CIA's website inaccessible on Friday - but later said it was just reporting the event.

The apparent distributed denial of service attack against the spy agency's web presence follows a week after the release of a recording of a conference call between the FBI and British law enforcement officials discussing the progress of various cases against alleged members of Anonymous and LulzSec.

A Twitter account associated with the activists' movement claimed credit for the takedown before backtracking and saying it was merely "noting" that the cia.gov site was inaccessible.

The initial statement "#Anonymous takes down main CIA website cia.gov; site is still down | goo.gl/UL2ij" was followed by "We'd remind media that if we report a hack or ddos attack, it doesn't necessarily mean we did it... FYI" from the same YouAnonNews Twitter account a day later.

The conflicting statements have created a certain amount of confusion about who was responsible for the outage.

A CIA representative confirmed problems with the agency's website without commenting on the reasons for the downtime, saying: "We are aware of the problems accessing our Web site, and are working to resolve them."

The cia.gov site returned to normal operation on Saturday. The site (which essentially serves as an online brochure for the spy agency and an outlet for public relations material) has been the target of hacktivists in the past, including a June 2011 attack by LulzSec.

Other elements of Anonymous launched attacks against the Mexican Senate and Interior Ministry websites, in a protest against proposed Mexican anti-piracy laws that hacktivists compared to the SOPA legislation north of the border.

And in a further attack against US law enforcement, other hacktivists posted (partially redacted) information swiped from police and government servers in Alabama.

Hackers claimed they had obtained highly sensitive personal information on 46,000 Alabama residents, including names, Social Security numbers, dates of birth, criminal records, and license plate numbers from insecure state government servers. A censored version of a sample of the hacked data was uploaded to PasteBin.

Anonymous said the hack was in protest against controversial Alabama state immigration laws. ®

Remote control for virtualized desktops

More from The Register

next story
'Regin': The 'New Stuxnet' spook-grade SOFTWARE WEAPON described
'A degree of technical competence rarely seen'
You really need to do some tech support for Aunty Agnes
Free anti-virus software, expires, stops updating and p0wns the world
You stupid BRICK! PCs running Avast AV can't handle Windows fixes
Fix issued, fingers pointed, forums in flames
Privacy bods offer GOV SPY VICTIMS a FREE SPYWARE SNIFFER
Looks for gov malware that evades most antivirus
Patch NOW! Microsoft slings emergency bug fix at Windows admins
Vulnerability promotes lusers to domain overlords ... oops
HACKERS can DELETE SURVEILLANCE DVRS remotely – report
Hikvision devices wide open to hacking, claim securobods
prev story

Whitepapers

Why cloud backup?
Combining the latest advancements in disk-based backup with secure, integrated, cloud technologies offer organizations fast and assured recovery of their critical enterprise data.
Forging a new future with identity relationship management
Learn about ForgeRock's next generation IRM platform and how it is designed to empower CEOS's and enterprises to engage with consumers.
How to determine if cloud backup is right for your servers
Two key factors, technical feasibility and TCO economics, that backup and IT operations managers should consider when assessing cloud backup.
Reg Reader Research: SaaS based Email and Office Productivity Tools
Read this Reg reader report which provides advice and guidance for SMBs towards the use of SaaS based email and Office productivity tools.
The Heartbleed Bug: how to protect your business with Symantec
What happens when the next Heartbleed (or worse) comes along, and what can you do to weather another chapter in an all-too-familiar string of debilitating attacks?