Oct 9, 2006

[Google] Official Blog Hacked

There's nothing quite like the blogosphere, really. With people around the world in different time zones, someone is inevitably going to catch something of interest that will only exist for a few hours, or perhaps even a few minutes.

Ironically, my last update to the Geeky Guide touched on Google's security efforts as they had discussed in a recent blog entry, which all in all seemed a good thing across the internet. The irony lies in the fact that this same official blog hosted on Blogger was hacked.

A false entry was posted describing the end of the Click-to-Call project. It was a very brief blog entry and read thus:

After concientiously considering, Google has decided not to continue with Google Click-to-call project. The project has been in the media on last days because of the notice of Google agreement with e-Bay. We finally consider click-to-call agreement with e-Bay a monopolistic aproach that would damage small companies in the CRM area.

This message has been translated using Google language tools.

Weird message, huh? The fact that there's a not about this being a translate message had bloggers across the globe scratching their heads trying to figure it out. The Googlified blog was one of those that caught the hacker post and quickly spread the word about the strange entry.

Google quickly found the breach and deleted the false post ASAP, along with quickly posting a brief statement using the official blog.

While this is a rather minor security mishap given any company and not just Google, it's just sort of amusing seeing it now right after last week's big statement about increased focus on security.


  1. Not irony, simply coincidence.

  2. of everyone has their right to their opinions.

    at this point, i keep thinking along the lines of "a rose being a rose" and all that - whether irony or coincidence, you have to admit the timing was pretty interesting.

    i'm sure some would take their assumptions further and assume the hacking was a direct response to the security post, or something else alongs those lines.

    i'm just concerned that it happened at all.