DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

CloudFare breach cause for concern (updated)

Posted on June 2, 2012 by Dissent

Given the number of hacks revealed on a daily basis, I long ago gave up on trying to mention them all on this blog, but this one merits its own entry.

Eduard Kovacs reports that although CloudFare has acknowledged it was compromised, the co-founder and CEO may not be correct in his understanding of the breach:

“This morning a hacker was able to access a customer’s account on CloudFlare and change that customer’s DNS records. The attack was the result a compromise of Google’s account security procedures that allowed the hacker to eventually access to my CloudFlare.com email addresses, which runs on Google Apps,” Prince explained.

He believes that the attackers somehow “convinced” Google’s account recovery process to add an arbitrary recovery email address to his personal Gmail account.

“The password used on my personal Gmail account was 20+ characters long, highly random, and not used by me on any other services so it’s unlikely it was dictionary attacked or guessed,” he added.

The most interesting fact, according to Prince, is that his account had been protected with a two-factor authentication system.

After analyzing the incident, Google’s security team has determined that “a subtle flaw in the recovery flow” of certain accounts allowed the hackers to compromise the account.

But the hackers involved claim that that’s not what happened:

“Nah. There’s no way you can social engineer a Google App. I don’t know what he was talking about. We did get in his emails though: [email protected] and [email protected],” Cosmo told Softpedia.

“We got into their main server. We could see all customer account information, name, IP address, payment method, paid with, user ID, etc. and had access to reset any account on CloudFlare,” he said.

Furthermore, the hackers plan on selling all the information they obtained on Darkode.

This type of hack – where the hackers intend to sell the data they acquired – takes things to a whole other level. If you’ve used Cloudfare, you should probably be taking steps immediately to protect your accounts. And if the hackers are truthful – that this had nothing to do with Google’s two-factor authentication – then it may mean that CloudFare is still insecure or vulnerable to a repeat compromise, which could affect the company’s ability to earn existing and potentially new customers’ trust.

Hopefully, CloudFare will respond to the hackers’ assertions with an update to their blog.

Update: CloudFare updated their blog with a more detailed explanation of how the information may have been obtained and it’s not quite what they thought originally, but kudos to them on their disclosure of social engineering so that everyone can learn how to protect themselves better.

Category: Breach IncidentsBusiness Sector

Post navigation

← 4Chan.org Hacked, Defaced and data stolen & Statement for Admin – by #UGNazi
China Bearing Commercial Community Hacked, 30,000+ Accounts Leaked @DeadMellox →

1 thought on “CloudFare breach cause for concern (updated)”

  1. JJ says:
    June 4, 2012 at 8:53 am

    This is actually CloudFlare, a DDoS mitigator. They had a write-up awhile ago when LulzSec was using them to keep their site up during their rampage. http://www.it-networks.org/2012/03/01/how-cloudflare-kept-lulzsec-safe/

    This had the potential to redirect every single one of CloudFlare’s customers to phishing sites.

Comments are closed.

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • Twilio denies breach following leak of alleged Steam 2FA codes
  • Personal information exposed by Australian Human Rights Commission data breach
  • International cybercrime tackled: Amsterdam police and FBI dismantle proxy service Anyproxy
  • Moldovan Police Arrest Suspect in €4.5M Ransomware Attack on Dutch Research Agency
  • N.W.T.’s medical record system under the microscope after 2 reported cases of snooping
  • Department of Justice says Berkeley Research Group data breach may have exposed information on diocesan sex abuse survivors
  • Masimo Manufacturing Facilities Hit by Cyberattack
  • Education giant Pearson hit by cyberattack exposing customer data
  • Star Health hacker claims sending bullets, threats to top executives: Reports
  • Nova Scotia Power hit by cyberattack, critical infrastructure targeted, no outages reported

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • FTC dismisses privacy concerns in Google breakup
  • ARC sells airline ticket records to ICE and others
  • Clothing Retailer, Todd Snyder, Inc., Settles CPPA Allegations Regarding California Consumer Privacy Act Violations
  • US Customs and Border Protection Plans to Photograph Everyone Exiting the US by Car
  • Google agrees to pay Texas $1.4 billion data privacy settlement
  • The App Store Freedom Act Compromises User Privacy To Punish Big Tech
  • Florida bill requiring encryption backdoors for social media accounts has failed

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net

Mastodon: Infosec.Exchange/@PogoWasRight

Signal: +1 516-776-7756

DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.