WordPress.Com Hacked, Hacker Root the Server !
The parent company that operates WordPress, made an announcement this morning that it has hacked, resulting what the company said was a low-level (root) break-in to several of their servers. The company warned that potentially anything on those servers could have been revealed to the attackers, including client source code.
WordPress founder, Matt Mullenweg made the following announcement in a blog post this moring. Read here
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.
Based on what we've found, we don't have any specific suggestions for our users beyond reiterating these security fundamentals:
• Use a strong password, meaning something random with numbers and punctuation. • Use different passwords for different sites.
• If you have used the same password on different sites, switch it to something more secure.
(Tools like 1Password, LastPass, and KeePass make it easy to keep track of different unique logins.)
Our investigation into this matter is ongoing and will take time to complete. As I said above, we've taken comprehensive steps to prevent an incident like this from occurring again. If you have any questions or concerns, please leave a comment below or contact our support.
The parent company that operates WordPress, made an announcement this morning that it has hacked, resulting what the company said was a low-level (root) break-in to several of their servers. The company warned that potentially anything on those servers could have been revealed to the attackers, including client source code.
WordPress founder, Matt Mullenweg made the following announcement in a blog post this moring. Read here
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.
Based on what we've found, we don't have any specific suggestions for our users beyond reiterating these security fundamentals:
• Use a strong password, meaning something random with numbers and punctuation. • Use different passwords for different sites.
• If you have used the same password on different sites, switch it to something more secure.
(Tools like 1Password, LastPass, and KeePass make it easy to keep track of different unique logins.)
Our investigation into this matter is ongoing and will take time to complete. As I said above, we've taken comprehensive steps to prevent an incident like this from occurring again. If you have any questions or concerns, please leave a comment below or contact our support.
