Skip to content


18 Million WordPress Blogs Compromised In Attack

WordPress, the blogging platform that powers more than 18 million blogs on WordPress.com, announced this morning that its servers had been broken into and source code, among other things, could have been exposed.

WordPress founder Matt Mullenweg writes “Tough note to communicate today: Automattic had a low-level (root) break-in to several of our servers, and potentially anything on those servers could have been revealed.”

Sponsor

According to Mullenweg, the break-in was limited but proprietary information could have been accessed:

We have been diligently reviewing logs and records about the break-in to determine the extent of the information exposed, and re-securing avenues used to gain access. We presume our source code was exposed and copied. While much of our code is Open Source, there are sensitive bits of our and our partners’ code. Beyond that, however, it appears information disclosed was limited.

TechCrunch’s Alexia Tsosis argues that Mullenweg is downplaying the severity of the incident, pointing out that “WordPress.com VIP customers are all on ‘code red’ and in the process of changing all the passwords/API keys they’ve left in the source code.” TechCrunch, among other big blogs, is a WordPress VIP customer.

“While Automattic is down playing the leak, site source code includes API keys and Twitter and Facebook passwords,” writes Tsosis.

Mullenweg says that the investigation is ongoing and that they have “taken comprehensive steps to prevent an incident like this from occurring again.” We have reached out to find out what other information might have been compromised and will update this story when Auttomatic responds.

Mullenweg also suggests that users should use strong passwords, different passwords for each site and, “If you have used the same password on different sites, switch it to something more secure.” In other words – change your passwords, folks.

Discuss


Posted in General, Technology, Web.

Tagged with .


0 Responses

Stay in touch with the conversation, subscribe to the RSS feed for comments on this post.



Some HTML is OK

or, reply to this post via trackback.