Looks like there is another WordPress exploit out there dubbed Gumblar .cn - I was actually made aware of it through a pingback from Growmap.com on their: Watch Out for Recent WordPress Gumblar PHP Exploit post.
These attacks are extremely time consuming to clean up, trust me I've had to do it before in the past. It's not a quick or easy thing to have to deal with at all.
There is also an excellent explanation of Gumblar here: Gumblar .cn Exploit - 12 Facts About This Injected Script
Please proactively protect yourself against this exploit!
Update: I'm quoting a bit from Scansafe's excellent Q&A about the exploit:
Is this a cross-site scripting (XSS) attack?
No. The compromises appear to be the result of stolen FTP credentials and direct manipulation of files on the Web server.
What is the intent of the malware distributed through the Gumblar compromised websites?
The malcode distributed via the compromised websites attempts to exploit PDF and Flash exploits in order to deliver malware that redirects infected users’ search engine results. In these particular attacks, the malcode appears to be targeting Internet Explorer users and Google search. In addition, the gumblar.cn malcode installs a backdoor that connects to 22.214.171.124 – an IP address of a known botnet command and control that has historically been associated with malware engaged in malicious redirections.
Reference blog post: http://blog.scansafe.com/journal/2009/5/8/google-serps-redirections-turn-to-bots.html
How do these malicious redirections work?
Similar to a man-in-the-middle attack, these redirections occur as a result of a man-in-the-browser attack. The malcode injects itself into the browser process, monitors the requests processed by the browser, and injects fraudulent traffic. In the case of the Google SERPs redirects, the malcode replaces legitimate Google SERPs results with links pointing to malicious or fraudulent websites.
Millions of websites have been compromised over the past year; what makes these particular compromises unique?
A typical series of website compromises reaches peak within the first week or so and subsequently begins declining in intensity as detection is added by signature vendors, user awareness increases, and website operators begin cleaning the affected sites. (This is why attackers are constantly pushing new waves of compromise).
In the gumblar.cn attacks, the opposite is occurring. As website operators attempt to clean up the original compromise or otherwise make changes to the original source code of the .htm, .php, and .asp pages on their sites, the gumblar.cn compromise is injected. The gumblar.cn mal-script appears to be dynamically generated and thus varies not only from site to site, but also from page to page on the same site. In addition, the resulting mal-script is heavily obfuscated, further hampering signature detection methods. As a result, the gumblar.cn compromises are increasing – up 188% from last week and a 61% increase from yesterday.
Here are some related articles I've written that might be helpful:
Best of Luck,