Hackers recently stole employees' user names, e-mail addresses and hashed passwords from AMD's official blog.

"The group, dubbed R00tbeer, broke into the site over the weekend and published a SQL file containing 185 AMD login details to file sharing websites," writes SC Magazine's Darren Pauli. "The purported account of AMD technology group general manager Checkib Akrout was included in the leaked files."

"Most (174 from 185) of the email addressees appear to relate to AMD and its PR representatives," writes The Register's John Leyden.

"A few of the records also include an intriguing - but unexplained - field called user_activation_key," notes Sophos' Paul Ducklin. "Whatever those are, it would be a good idea for AMD to deactivate them and issue new ones."

"The leak included data from July 2010, and as recent as 9 August this year," writes ZDNet's Michael Lee.

"R00tbeer seems to be a new player on the scene," writes TechWeekEurope's Max Smolaks. "The group opened a Twitter account on 18 August, and had assembled 233 followers at the time of this story being published."

"The main page of the blog -- located at blogs.amd.com -- [was] defaced to include the group's logo, member names and a link to its (recently opened) Twitter account," writes Help Net Security's Zeljka Zorz. "Given that AMD uses the WordPress platform for its blog, it's very likely that the breach was the result of not keeping the software updated, allowing the attackers to exploit vulnerabilities present in some previous version."

In response, AMD issued the following statement to Softpedia: "AMD's blog site was the target of an attack on August 19th. We believe that the attackers posted less than 200 registered usernames and salted password hashes to a hacker web site. AMD uses salted password hashes, which is an industry best practice for encryption and extremely difficult to crack. We immediately took the blog site offline and changed all passwords. AMD remains committed to data security and user privacy and has launched an investigation into this matter. We expect to bring our blog site back online within the next 24 hours."