Share

Related Links

Related Stories

  • Assange: asylum crunch day
    WikiLeaks founder Julian Assange, wanted by Sweden (definitely) and the US (probably) is inside the Ecuadorean embassy in London seeking political asylum. Today, Thursday 16 August, is the day that Ecuador has said it will announce its decision.
  • WikiLeaks taken out by sustained 10GB/sec DDoS attack
    On 4 August a new group appeared on Twitter with a simple announcement: “Anti Leaks: Tango down wikileaks.org #Wikileaks #Cowards”. Since that time WikiLeaks and its affiliate sites and mirrors have remained unavailable or severely disrupted.
  • WikiLeaks starts to publish Syrian emails
    Yesterday WikiLeaks started to publish the Syria Files: 2,434,899 emails with 1,082,447 different recipients from 680 domains. The total size of the dataset is said to be eight times the number of documents contained in ‘Cablegate’, and 100 times its size.
  • WikiLeaks redux: Site teams with hacktivists to publish Stratfor emails
    WikiLeaks is back in the news. The site dedicated to leaking state secrets has teamed with Anonymous to disclose emails from intelligence firm Stratfor, which Anonymous offshoot LulzSec breached in December.
  • WikiLeaks denounces its exclusion from UNESCO conference
    WikiLeaks has denounced UNESCO for refusing to allow it to speak at a conference being held at UNESCO HQ in Paris today and tomorrow. The conference is called 'The Media World after WikiLeaks and News of the World.'

Top 5 Stories

News

CloudFlare helps restore WikiLeaks

16 August 2012

After more than a week of persistent DDoS attack by Anti Leaks, WikiLeaks is now available again, courtesy, it says, of increased capacity and CloudFlare protection.

On 4 August, a new account on Twitter under the name of Anti Leaks announced, “Tango down wikileaks.org.” For more than a week, WikiLeaks remained either down or severely disrupted. Finally, on 13 August, WikiLeaks announced, “WikiLeaks is back open after installing substantial extra capacity and additional help from @cloudflare caching http://wikileaks.org/.”

During the attack, WikiLeaks said it faced a DDoS of well over 10Gbits/second and directed by someone able to control or simulate thousands of machines. It added, “We have even tried moving behind http://Cloudflare.com but Cloudflare has [p]re-emptively banned WikiLeaks.”

This, it seems, was procedural rather than decisive. WikiLeaks is now protected by CloudFlare. “CloudFlare CEO Matthew Prince told [TechCrunch] that Wikileaks switched over to CloudFlare [on Monday] and was back online within minutes.”

Traffic for CloudFlare’s customers are routed through CloudFlare servers which block any illegitimate traffic. In this way, CloudFlare is effectively a cloud-based firewall; but with the advantage that it learns as it goes. “We throw ourselves in the way of DOS attacks because it makes our network more resilient,” said Prince. “It’s like strengthening your immune system.” And so far it is working.

The battle, however, is not over. Anti Leaks taunted CloudFlare on Twitter, “You must feel really good about yourselves #CloudFlare for hiding and protecting criminals like Wikileaks and Lulzsec. #Bloodmoney.” (CloudFlare had earlier protected the hacking group LulzSec, but “We don’t discriminate against customers based on a political belief of what’s good or bad,” explained Prince. “We try hard not to play censor.”) But yesterday an Anti Leaks spokesperson known as DietPepsi indicated the attacks would continue. “I am in the process of finding the actual IP address of WikiLeaks web server. I have a couple of leads and believe I will be able to do it, however it will take some time,” he said in an email to The Register.

This article is featured in:
Business Continuity and Disaster Recovery  •  Cloud Computing  •  Internet and Network Security

 

Comment on this article

You must be registered and logged in to leave a comment about this article.

We use cookies to operate this website and to improve its usability. Full details of what cookies are, why we use them and how you can manage them can be found by reading our Privacy & Cookies page. Please note that by using this site you are consenting to the use of cookies. ×